Overview
Roles and permissions determine what each person can see and do in a Scrambl workspace. They affect visible modules, available actions, sensitive settings, and sometimes access to individual records or collaboration areas.
Use this article as a plain-language introduction before configuring detailed access levels in Settings → Administration → Members → Access levels or inviting people from Settings → Administration → Members.
Core concepts
| Concept | What it means | Example |
|---|---|---|
| Organization role | A broad label for someone's place in the workspace. | Owner, admin, member, contractor, finance user, or another team-defined role. |
| Access level | The specific actions a person can take in each module. | Read projects, create tasks, manage invoices, or update members. |
| Record access | Access that depends on a specific record, assignment, relationship, or collaboration scope. | A user can view one project but not another. |
| Plan availability | Whether the workspace subscription includes a feature at all. | A Business-only feature may not be available in a Pro workspace. |
Important: Permissions and plan availability are different. A user can have permission for a module only if the workspace plan includes that feature.
How permissions affect the workspace
- Users see only the modules their role allows them to access.
- Users may be able to view a record without editing it.
- Some actions, such as deleting records or managing settings, may be limited to admins.
- Sensitive modules such as finance, billing, integrations, subscription, and permission management should be restricted.
Use least access when inviting people
- Identify the work the person needs to do now.
- Choose the smallest role and access level that supports that work.
- Invite the person from Settings → Administration → Members.
- Ask them to test the first workflow they need, such as opening a project or updating a task.
- Expand access only if a real workflow requires it.
Sensitive access checklist
| Access area | Why it is sensitive | Review cadence |
|---|---|---|
| Members and permissions | Can change who can access the workspace. | After onboarding, role changes, and offboarding. |
| Billing and subscription | Can expose payment, plan, or subscription information. | Before finance handoffs and plan changes. |
| Contracts, invoices, and budgets | Can expose commercial terms, rates, and revenue data. | Monthly or when finance roles change. |
| Integrations | Can connect external systems and affect data flow. | Before connecting or removing tools. |
Troubleshooting
- A user cannot see a module: Check their role, access level, workspace plan, and organization context.
- A user can view but not edit: Review create, update, manage, or delete permissions for that module.
- A user sees too much: Move them to a narrower access level and review sensitive access.
- An external collaborator needs access: Review external user guidance before giving broad internal member access.
Next steps
Review the detailed permissions overview, then audit members after the first week so access matches how people are actually using the workspace.