Four system profiles
Choose a starting point for different project collaboration needs.
AMS · Connected business workflows
Permissions & scopes — Share the work. Keep the boundaries.
Control who can act, which project details they can change and what data they can see.
Who this helps
Workspace administrators and project leads deciding what different teammates should be able to see and do.
The situation
A manager needs a broad view, while a contributor should work within an appropriate set of actions and records.
Fictional example: compare the displayed Project manager matrix with a Member view and assigned-record scope. This website example makes no live changes.
Follow the example, step by step
Start with the role’s responsibilities
- What you do
- Inspect the Project manager example in the action matrix.
- What changes
- The matrix shows permissions across project resources and their actions.
- Why it helps
- You can assess what the role needs to do rather than relying on a title alone.
Compare a contributor’s actions
- What you do
- Use the Member control to compare the example’s read, own-update and denied actions.
- What changes
- The selected role has a more limited action matrix.
- Why it helps
- The difference between reading work and changing it becomes explicit.
Check which records are visible
- What you do
- Inspect the assigned-record example alongside the member permissions.
- What changes
- The scope panel shows one assigned record instead of the broader sample list.
- Why it helps
- You can consider visibility separately from permission to perform an action.
Review the combination
- What you do
- Compare the role and scope views before applying the intended configuration in your workspace.
- What changes
- The two panels keep allowed actions and accessible records visible together.
- Why it helps
- The access decision can reflect the person’s actual responsibility.
What your team gains
The team can discuss action permissions and visible records as two separate access decisions.
Set access at the layers that matter: role, project action and data visibility.
Inside Permissions & scopes
Project role permissions
Control actions across 17 project sub-resources.
Allow, deny or own
Use ownership-sensitive permissions where supported.
Task visibility
Distinguish access to all project tasks from assigned tasks.
Organization scopes
Control which records a user can reach at the resource level.
Separate access layers
A project action permission and an organization data scope answer different questions.
Questions and requirements
Is the displayed matrix a system profile’s default?
No. It is an illustrative role matrix. AMS provides Standard, Restricted, Open Collaboration and Client Portal starting profiles; actual project access follows the configured project snapshot and applicable organization controls.
Does selecting a role here change someone’s access?
No. These controls only compare fictional examples. Real changes require the relevant administration permissions, and project action permissions and organization data scope remain distinct controls.
Requirements and limits
The displayed role matrix is an example, not the default of a named system profile. Access follows the configured project snapshot and applicable organization controls.
Understand the next tool here
Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.
Projects & tasks — read how it fits
Set suitable collaboration permissions for the project people will work in.
Give every task an owner, a deadline and the context to move forward.
Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.
Before you use it
Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.
Optional: explore the full Projects & tasks story ↗AI assistant — read how it fits
Available assistant operations also depend on the signed-in user’s access.
Use a conversational assistant to help with the AMS work you are authorized to access.
Fictional example: a teammate asks, “Find the Autumn launch project,” and sees an illustrative accessible result.
Before you use it
AI needs a configured provider. Available tools vary with permissions and configuration. The visual is a website explanation, not a recorded assistant execution.
Optional: explore the full AI assistant story ↗