Change a member's permissions
Change an individual member's permissions to control whether they can view, comment on, edit or administer a team and it's content. Review the member's role and inheritance separately when deciding what access they need.
To understand how individual permissions and inherited memberships determine access, see How Teams and permissions work in Simana.
Before you start
- You need Admin access to the team your changing permissions for. If this is the organisation's team you will need to be an Organisation Admin user.
- Identify the member and the access they need.
1. Find the member
- In Manage organisation (when changing organisation level permissions), select the cog beside Team.
- Find the person under Users. Use Find members... or Show more if needed.
- Select the cog beside their name to open Configure member.
- Check the name at the top of the panel before changing anything.
2. Review and change their permissions
Under Permissions, review the following controls:
| Permission | What the interface explains |
|---|---|
| View | Allows the user to open and look at content, without changing it or interacting with it. |
| Comment | Allows the user to post comments in Threads. |
| Edit | Allows changes to content, including fields and moving items, but excludes Team and permission settings. |
| Admin | Gives control over the Team and permissions, including adding or removing users and changing their permissions. |
Use the switches to set the access the member needs.
Important: Grant Admin only to people who should manage the Team and other members' access.
3. Check permission dependencies
The panel explains these dependencies:
- Comment requires View.
- Edit requires Comment.
- Admin requires Edit.
A lower permission's switch is disabled while a higher permission requires it. For example, to reduce the permissions on this individual member record from Admin to View only, remove Admin, then Edit, then Comment, leaving View enabled. Review inherited access separately, as described below.
Note: A disabled switch does not necessarily mean you cannot manage that member. Read its dependency explanation first.
4. Review inheritance
Under Inheritance, review Inherit to child teams. When enabled, it carries this member’s membership and permission set into child teams, including across a Board’s permission boundary. Change it only when you intend to change how this membership applies to child teams.
A member can receive access through an inherited membership as well as through their individual record on a Board’s Team.
Important: Setting a member’s individual Board permissions to View does not override Edit received through an inherited organisation membership. They retain Edit through that inherited membership. When reducing access, review all memberships that provide it, including inheritance from the organisation Team.
The Role selector is a separate control. Use Assign a role to a member for that task.
5. Check the result
Close and reopen the member configuration to check the settings. Confirm that the member has the intended access.
Important: Delete member is a separate action. It is not required to change permissions.