Organisation
Available to organization administrators as part of the roles and permissions rollout.
The Organisation area is where administrators manage everything that spans teams. It is a separate destination — team switching and per-team settings stay where they are.
Where to find it
Open the account menu (your avatar, top of the sidebar) → Organisation. The entry appears only for organization administrators — users holding an organization-level role such as Organisation Admin. Screening, risk and review settings remain configured per team.
The area has its own menu, and each page appears only if your roles carry the permission behind it:
| Page | What it is for |
|---|---|
| Users & access | Everyone with access to the organization, their organization roles and their team memberships. |
| Roles & permissions | The role catalogue, and where your own custom roles are built. |
| Activity | One activity log across every team. |
| Identity federation | Provisioning from your identity provider, and the mapping from its groups to Strise teams and roles. |
Users & access
Everyone with access to the organization, one row per person — someone who belongs to several teams appears once, not once per team.
| Column | Contents |
|---|---|
| Name | Name and email. |
| Organisation role | Roles held at the organization level, which apply across every team. A dash means none. |
| Teams | The teams the person belongs to. A padlock marks a team your identity provider provisions. |
| Last active | When they last signed in. On the Deactivated tab, when and by whom. |
Two tabs split the list by state: Members (active) and Deactivated. An organization connected to an identity provider also gets a Directory tab, listing people the provider has provisioned who have no access yet. Search matches name, email or team, and the Role and Team filters narrow the list further — pick several roles to see anyone holding any of them, or No organisation role for people whose access comes only from their teams. Long lists are paged, 10, 25 or 50 people at a time.
Viewing and changing one person's access
Selecting a row opens a panel with that person's access:
- Roles assigned at organisation level — an organization role applies in every team, including teams created later. What it grants is whatever that role's permissions say, not automatically full access.
- Teams — every team the person belongs to, with their roles there. Change roles or remove them from a team without switching teams first.
Deactivating someone
The row menu deactivates a person across every team in the organization at once, keeping their memberships and roles so the change can be undone by reactivating them. It is not the same as removing them from a team, and it does not affect any access they have at another organization. You cannot deactivate your own account.
Deactivation is unavailable for anyone your identity provider provisions — remove them there instead. The last person holding the Organisation admin role can be neither deactivated nor stripped of that role: assign it to someone else first.
Changing several people at once
Tick people in the table and a bar replaces the filters with actions that apply to everyone selected: Add or remove teams, Set or remove roles and Deactivate; the Deactivated tab offers Reactivate. Adding to a team gives the new members the Analyst role, which the roles dialog can then change. Setting roles replaces what each person holds in the chosen teams — every team they belong to, or one — and only for people already in those teams; nobody is added to a team by it. Teams your identity provider provisions are skipped, and you are never deactivated by your own selection. Each action is one entry per person in the Activity log.
Inviting
Invite users takes a few names and addresses; Bulk invite takes a pasted list or an uploaded
CSV/text file and reads names from Name <name@company.com> rows or from the address itself. Both
then ask which teams the new members join, with one role per team (Analyst unless you pick another),
and the short form can also grant a role at organisation level. Addresses outside your organisation's
email domains are held back.
An invitation does not expire. The invited person logs in with a login code, so there is no link to use up. The email links to the Strise login page; see How to Log In.
Roles & permissions
The role catalogue for the organization, and the builder for your own roles when the built-in ones do not fit. Documented in Roles & Permissions.
Activity
One log of every access change across the organization and all its teams, filterable by actor, action, team and time range. Documented in Activity Log.
Identity federation
Where an organization connects its identity provider so users are provisioned and deprovisioned automatically, and maps identity-provider groups to Strise teams and roles. The page is shown to administrators who hold the identity-federation permission; talk to your customer success manager before setting it up.
Everything in the Organisation area is permission-checked against your organization-level access: a team-level administrator cannot reach it, and every action is enforced server-side at the organization node.
Last updated on