Role changed, access didn't
A member moved to a different responsibility internally and suspects their old permissions never got updated. They send a review request so an Owner can check and adjust their access to match the new role.
Request Organisation Access Review
Not sure your access level in an organisation still matches your role? Any non-Owner member can send a review request to every Owner in one action, prompting them to check and confirm what that member can currently do.
Permissions can drift as teams grow: a member's role gets reassigned, new capabilities get added, or an old grant never gets revisited. Request Organisation Access Review gives any non-Owner a direct way to flag their own access for a check, instead of waiting for someone to notice.
Triggering the request sends a notification to every Owner of the organisation at once. There is no queue to join and no separate approval workflow: it simply puts the request in front of the people who can act on it, at the same time.
It is deliberately narrower than Customize Access, the tool Owners already use to grant or revoke permissions directly. Customize Access is Owner-initiated and changes things immediately; Request Access Review is member-initiated and changes nothing by itself. Owners already have full organisation access by definition, so the request is scoped to members below Owner level. This keeps the feature focused on the case it exists for: a member checking that their current permissions match what they actually need.
It is worth saying plainly what a review is not. It is not an escalation, not a complaint, and not a request for more power. Nobody outside the Owners is told about it, no queue is created, and nothing about your membership changes at the moment you press it. All it does is put a question in front of the only people who can answer it: does this person still have the access their job needs, no more and no less.
Before you ask, you can check for yourself. The same page carries your effective access and the full permission matrix, so you can see exactly what you hold today and compare it against what everyone in each role can do. Quite often that answers the question on its own, and when it does not, the request button is right there next to the answer you were looking at.
The reason this exists at all is that permission drift is almost never noticed by the person who caused it. An Owner who reassigns work rarely thinks about the settings behind it; the person whose job changed is the one who hits the wall, or who quietly keeps access they no longer need. Letting that person raise their hand turns a periodic audit somebody has to remember into something that happens the moment it actually matters.
Who can request a review
Any accepted, non-Owner member of an organisation can send the request. Owners are excluded because they already hold full organisational access; there is nothing for them to have reviewed.
The request is scoped to the organisation the member is currently working in, so it only reaches the Owners of that specific organisation, never a different one the member might also belong to.
The button lives on Settings > Organizations > Roles, alongside your own effective access and the full permission matrix, so you can see exactly what you currently hold before asking for it to be checked.
What Owners see
Every Owner on the account gets their own notification when a request comes in, so the ask does not depend on one specific person being online or checking a shared inbox.
The notification identifies the requesting member so an Owner can go straight to that person's membership settings and check their role and permissions against what they should have.
The notification is in-app only, not emailed. If the same member requests a review more than once within a five-minute window, only the first triggers a fresh notification, so repeated clicks do not flood each Owner's bell.
What an Owner can actually adjust
An Owner reviewing a member's access can override five permissions per membership without changing their role: viewing team members, inviting new members, managing non-Owner members, managing resource access, and managing billing. The first four follow the role by default. Billing does not: it stays with Owners unless an Owner deliberately hands it to one person, which is how a workspace stays payable when the Owner is away.
One capability never moves to an override, no matter what the review request asks for: organisation control, meaning renaming, deleting, or otherwise altering the workspace itself, stays with Owners only. A review can surface a gap in the delegable permissions; it can never be used to push organisation-level control onto a Collaborator or Admin.
A workspace must always retain at least one Owner, so a review can never result in the last Owner losing that role as a side effect.
How It Works
One request, every Owner notified
A member opens the request from their organisation settings. The platform confirms they belong to that organisation and that they are not already an Owner, then looks up every accepted Owner membership on the account.
Each Owner receives an access review notification naming the member who asked and pointing at their current membership. Owners can then open that member's permissions and adjust them directly if a change is warranted.
The request itself does not change any permissions. It is a signal, not a mutation: the actual review and any resulting change stays a deliberate action taken by an Owner.
Use Cases
Onboarding cleanup
A member added early in the organisation's setup, when permissions were looser, wants confirmation that their access still makes sense now that the organisation has grown. One request notifies every Owner to take a look.
Self-service instead of a support ticket
Rather than messaging an admin outside the platform to ask about their access level, a member triggers the request directly from Settings > Organizations > Roles and lets the notification do the routing.
You keep hitting a wall you should not be hitting
Something you need for your job is refused, and you cannot tell whether that is deliberate or an oversight. Rather than guessing or working around it, one request puts your membership in front of every Owner so the answer comes back as a decision instead of a shrug.
Comparison
| Before | After |
|---|---|
| Asking about your access means messaging somebody outside the platform and hoping they see it. | One button in your organisation settings notifies every Owner at once, inside the app. |
| You only discover what you are allowed to do when something refuses to work. | Your effective access and the full permission matrix sit on the same page as the request button. |
| An access request either changes nothing or quietly hands over more than intended. | The request itself changes nothing; every adjustment stays a deliberate action an Owner takes. |
| Chasing the one admin who might be on holiday means waiting days for an answer. | Every Owner gets their own notification, so the ask never depends on one person being online. |
FAQ
Does requesting a review change my permissions automatically?
No. The request only sends a notification to Owners. Any change to your role or permissions is a separate, deliberate action an Owner takes afterward, using Customize Access on your membership.
Can Owners request a review of their own access?
No. Owners already have full organisation access, so the request is only available to members below Owner level.
Who receives the notification when I request a review?
Every accepted Owner on the organisation receives their own copy of the request, not just one designated admin. It arrives as an in-app notification, not an email.
Can I request a review for someone else?
No. The request always covers your own membership and permissions; it is not a way to flag another member's access.
What can an Owner actually change after my review?
Five permissions can be overridden per membership: viewing team members, inviting members, managing non-Owner members, managing resource access, and managing billing. Billing is Owner-only by default and only moves when an Owner grants it deliberately. Organisation-level control, such as renaming or deleting the workspace, always stays with Owners.
What happens if I click the request button more than once?
Repeated requests from the same member within a five-minute window are throttled to a single notification per Owner, so it will not spam their notifications if you click it again by accident.
How do I check what I am currently allowed to do in a workspace?
Open Settings > Organizations > Roles. That page shows your own effective access alongside the full permission matrix for every role, so you can see exactly what you hold today. The request button sits on the same page for when the answer is not what you expected.
Will other members see that I asked for an access review?
No. Only Owners receive the notification. Other Admins and Collaborators are not told, nothing appears on a shared list, and the request leaves no public mark on your membership.
Where Request Organisation Access Review fits
Request Organisation Access Review is part of How you run the account itself.
Sign in the way your company already does, decide who can do what, and keep the money side legible. Credits, plans, invoices, referrals, and the controls that decide who reaches which part of the workspace.
- How you run the account itself: Your workspace, your money, your people.
Read the guide
More in Account & Billing
- Monthly Credits: Every paid plan comes with a pool of credits that refills automatically at the start of each billing period. Credits are the single unit that pays for everything your AI employees do: thinking, tool calls, media generation, voice, and meetings. There is nothing to top up manually each month; your allowance is just there again when the new period starts.
- Lifetime Credits (Free): Pick the Free plan and your workspace gets 2,000 credits in one grant, no card required. Those credits never reset and never expire; you spend them at your own pace across chat, tools, and media generation until they run out. It is a one-time bucket, not a monthly allowance, so it is meant for trying the platform before you commit to a paid plan.
- Buy Credits: Add credits to your workspace balance any time, on any plan, without changing your subscription. Pick from three one-time packs, pay by card through Stripe, and the credits land in your balance as soon as the payment clears.
- Upgrade & Downgrade: Move to a bigger plan the moment you need more credits or a higher employee cap, and the change takes effect immediately. Move to a smaller plan when you need less, and it takes effect at the end of your current billing period so you keep what you already paid for. Both happen from Settings, Subscription, no support ticket required.
- Promo Codes: Redeem a promotional code for a one-time, lifetime grant of bonus credits on top of your plan's monthly allowance. Enter a code at signup or any time afterward from Settings, Subscription, Get Free Credits. Each grant shows up in your Credit Grants history with its source, date, and amount, and one code can be redeemed once per workspace.
- Referrals: Share your personal referral link or invite someone by email, and you both get 1,000 free credits the moment they sign up. Track every invite from a dedicated Earn Credits page, and keep earning until you hit the 10-referral cap.
- Data Retention: Sistava deletes operational data on a fixed schedule instead of keeping it forever by default. A cleanup job runs every day and removes rows past their retention window: short-lived debug data within a week or two, working memory after 30 days of inactivity, and usage and activity history after two years. Chat messages, documents your employees write, and persistent notes are kept indefinitely unless you delete them yourself. There is no setting to change these windows; they apply the same way to every workspace.
- Google Sign-In: Sign in to Sistava with your Google account instead of creating a separate password. Choose Sign up with Google on the signup page and your workspace is ready after one approval, with your name and photo carried over automatically from Google. Because Google has already confirmed your email address, there is no verification email to chase before your AI employees can start working.
- Microsoft Sign-In: Sign up or sign in with your Microsoft account instead of creating a password. Sistava reads your Microsoft account's name, email, and profile photo to set up your account, and your Profile page shows Microsoft as your connected sign-in method. Because Microsoft has already confirmed the address belongs to you, the account counts as verified from the start and your employees can begin working straight away. Google sign-in and an ordinary email and password are the other two ways in.
- Workspace Roles: Every workspace you create has an Owner, Admin, and Collaborator role, each with a fixed set of permissions over billing, the collaborator roster, and resource access. Owners can grant a non-owner collaborator extra access, or take some away, without changing their overall role. A Roles page shows your own effective access and the full permission matrix so nobody has to guess what they can do.
- User Profile Picture: Upload a photo for your account so your teammates and AI employees see a real picture of you instead of initials. It shows up in chat, comments, and the collaborator list across every workspace you belong to. If you signed up with Google or Microsoft, your picture is pulled in automatically the first time you sign in, and you can replace it any time.
- Two-Factor Authentication: Add a second sign-in step to your Sistava account using any TOTP authenticator app, like Google Authenticator or Authy. Once enabled, a code from your app is required in addition to your password, so a leaked or guessed password alone is not enough to get in. Turning it on immediately signs out every other active session, so a session created before you enabled it cannot be used to bypass it.