Access Management
Settings → Access Management controls what each team member can do in bluefactory, with reusable roles. It's a simple, team-style permission model: create a role once, assign it to people.
Only account owners can create roles or assign them; members see these pages read-only. Owners themselves always have full access and can't be assigned a role.
Roles
A role grants an access level per module, and each module grant can be scoped to specific orgs.
The modules:
| Module | Covers |
|---|---|
| Backup & Restore | Back up Salesforce data and restore it |
| Archive | Archive and retrieve historical data |
| Sandbox Seeding | Seed sandboxes with production data |
| Change Tracker | Track metadata and configuration changes |
| Query & Insights | Query snapshots and explore data |
| Data Quality | Profile, dedupe and clean data |
The access levels: No Access · Read Only · Full Access.
The org scope — each module grant applies to: All organizations, Production orgs, Sandbox orgs, or Specific orgs you pick from a list.
Creating a role
- Go to Settings → Access Management → Roles and click Create role.
- Name it (e.g. Backup Manager) and add a description.
- For each module, pick an access level and the org scope it applies to.
- Save.
[SCREENSHOT REQUIRED: Create role form with the module access grid]
Typical roles teams create:
- Admin — Full Access to all modules, all organizations.
- Backup Manager — Full Access to Backup & Restore and Archive; Read Only elsewhere.
- Analyst — Full Access to Query & Insights and Data Quality on sandboxes; Read Only on production.
- Read Only — Read Only on everything.
Assignments
The Assignments tab binds roles to people — one role per user.
- Click Assign role.
- Pick one or more users (owners aren't listed — they always have full access).
- Pick the role.
- Confirm. Assigning replaces a user's current role; you can also Change or Remove an assignment from the list.
[SCREENSHOT REQUIRED: Assign role dialog with user list and role selector]
How access is decided
A member's access to a module in a given org is the level granted by their role for that module, if the role's org scope covers that org. No applicable grant means No Access. Deleting a role removes the assignments that used it.