Skip to content
MapleGatherMapleGather Help

Migration permissions reference

This page lists the permissions that control access to Migration & Onboarding features in MapleGather. Org Owners can assign these to admin roles in Settings > Admin roles.

Import permissions

Section titled “Import permissions”
Permission scope What it allows Who needs it
imports:read View the import history list, preview screens, error reports, and the relationship graph. Any admin who reviews or monitors imports.
imports:write Update column mappings, flag duplicates, commit an import (and Retry import on one that hasn’t finished after 15 minutes), and undo committed imports. Admins who actively run imports.
imports:create Start a new import (upload a file and create an import job). Admins who initiate imports.

The Org Owner role includes all three by default. If an admin can see the Migration section but can’t start a new import, check that imports:create is included in their role.

Historical import permissions

Section titled “Historical import permissions”

Not available yet. Historical data import and its reconciliation are planned, not built (see Historical import data types reference); the rows below describe the planned design.

Access to historical imports and reconciliation is gated by sub-role assignment. The exact API scopes for these operations are defined in your organization’s role configuration. Ask your Org Owner to assign the Finance sub-role or equivalent to anyone who needs to run historical payment imports or use the reconciliation panel.

Task What it allows Who needs it
Historical data import Import historical payments, membership tenure, and event registrations. Finance sub-role or equivalent.
Financial reconciliation Run the financial reconciliation panel in sandbox mode before committing a historical payment import. Finance sub-role or equivalent.

Wizard permission

Section titled “Wizard permission”
Permission scope What it allows Who needs it
migration:wizard Access and use the AI-assisted migration wizard, including the 6-step onboarding checklist. Any admin you want to allow to use the guided setup experience.

Broadcast permissions

Section titled “Broadcast permissions”
Permission scope What it allows Who needs it
migration:broadcast Create, send, cancel, and monitor the post-migration broadcast and transition dashboard. Admins who send the member welcome email and track adoption.
Section titled “Member permissions related to migration”

These tasks rely on permissions also used outside migration. The scopes are defined in the Member Database and Membership sections; they are listed here for quick reference.

Task What it allows Underlying permission area
View duplicate flags See the duplicate-member pairs flagged during import review. Member Database — members read (members:read)
View imported members Open Members showing only the members one import created (the View imported members link on a completed or undoing import). Member Database — members read (members:read)
Inline-create a membership level Create a membership level inline during column mapping. Membership — level management (see Membership Levels section)
Inline-create a custom field Create a custom member field inline during column mapping. Member Database — field management
Inline-create a tag Create a tag inline during column mapping. Member Database — tag management

Wild Apricot migration permissions

Section titled “Wild Apricot migration permissions”

Moving from Wild Apricot uses four additional permissions, alongside the import permissions above.

Permission scope What it allows Who needs it
migration:configure-api-source Connect to the Wild Apricot API and pull contacts, events, registrations, invoices, and payments. Admins running an API-based Wild Apricot migration.
migration:configure-file-source Connect to Wild Apricot’s WebDAV file storage and pull member files. Admins fetching Wild Apricot file attachments.
migration:import-content Upload and parse a Wild Apricot website archive, then review and accept its pages, blog posts, and forum threads. Admins bringing over Wild Apricot website content.
migration:reconcile Create, view, drill into, and export the Wild Apricot reconciliation report. Admins and finance staff confirming a Wild Apricot migration came across cleanly.

The Org Owner role includes all four by default. Reading or disconnecting a Wild Apricot connection works with either migration:configure-api-source or migration:configure-file-source — you don’t need both just to check a connection’s status.

Section titled “Related”