1Commando  /  Product  /  Access reviews
Compliance

Quarterly access reviews built from the graph.

The access review your SOC 2 or SOX auditor asks for, with the flagged grants first. Reviewers see why each grant was flagged and when it was last used, then approve it for one year or request its removal, with an optional reason.

Q3 2026 access review · Marlow Industrial
957 flagged
Sarah Mitchell
GitHub · prod-deploy environment
0 of 4 peers · unused 3.9 years
Removal requested
ramp-sync
Brex · Approver
no owner · last used 2026-03-02
Removal requested
Maya McCarthy
Salesforce · System Administrator
RevOps Manager · 2 of 41 peers
Approved for one year
3 decisions recorded, each with who decided, when, and why · Undo open for 30 minutes
Three flagged grants from the Marlow Industrial demo and a reviewer's decisions. The two removal requests stay open until the access is removed in the source system.
How it works
01

Generate

Choose a department or the whole organization, and flagged grants only or every restricted and confidential grant. Each row shows why it was flagged and when it was last used. The recommendation is Revoke for high-severity flags and for flagged grants unused for 90 days, and Approve otherwise.

02

Decide

Approve for one year or request removal, each with an optional reason, and undo within 30 minutes. 1Commando only reads from your systems, so a removal request stays open until the access is removed at the source and the next import shows it gone.

03

Record

Every decision is logged with who made it, when, and why. An approved grant stays out of the open queue for a year, then comes back for review. A decision undone within 30 minutes is removed from the log.

What you get

Access reviews, in practice.

  • Flagged grants only, or every restricted and confidential grant with the flagged ones first
  • Evidence per row: the flag reasons, last use, and a link to the trail with who granted each step
  • An auditor CSV with each grant, its recommendation, and the decision in force
  • A decision log CSV with who made each decision, when, the reason, and the expiry
Included · Disputes and exceptions In development

A flag you can argue with.

Managers and employees will be able to dispute a flag with a reason. An accepted reason will be stored on the grant with an expiry, and the flag stays closed until then. Approvals with a reason already work this way and hold for one year.

Flag · R. Chen · Snowflake CUSTOMERS
Flagged
Chief Financial Officer · 0 of 7 peers hold it · last used 2026-09-16
Dispute · reason given
"Rachel runs the monthly revenue queries herself until a finance analyst is hired."
Accept · expires 2027-03-01Decline
The CFO's access to the Snowflake CUSTOMERS schema is flagged because none of her 7 peers hold it. The demo org records an exception for it, accepted by D. Coleman and expiring on 2027-03-01.
01

Flag

A grant that does not fit is flagged with its reasons and evidence. The person and their manager will be notified.

02

Dispute

Either of them will be able to reply with a reason. The reviewer will see it next to the evidence and accept or decline.

03

Exception

An accepted reason will be stored on the grant with who accepted it and when it expires, the same way approvals are stored today. The decision log export shows it to auditors.

  • Fewer repeat flags
  • Reasons recorded for auditors
  • Exceptions that expire and come back for review
  • Reasons from the people who use the access
Included · Employee report card In development

Your own access, in one page.

Each employee will get a page that lists what they can reach and when they last used it, and they can mark what they no longer need.

Your access · Sarah Mitchell
51 grants · 13 flagged
NetSuite · Controller
used 2026-09-21
Brex · Bookkeeper
used 2026-09-21
Snowflake · FINANCE schema
used 2026-09-21
GitHub · prod-deploy environment
last used 2022-11-02
Removal requested
Slack · Workspace Admin
never used
Removal requested
Two removal requests sent to Travis Park, her manager.
The planned employee view, filled with Sarah Mitchell's demo data. She marks two unused grants, and the removal requests go to her manager.
01

See

A personal page will list every grant, when it was last used, and which domain it belongs to. Each company will choose whether to turn it on.

02

Flag

The person will tick what they no longer need. Nothing changes until their manager confirms.

03

Request removal

Removal requests will go to the manager and be recorded like any review decision. 1Commando only reads from your systems, so the access is removed at the source.

  • Opt-in per company, with the score kept private if you prefer
  • Employees will be able to point out their own unused access
  • A team view for managers
  • Fewer review rows once the access is removed at the source
Get started

See your own access graph.

Start with Okta or Google Workspace, plus a Workday export. 1Commando only reads from them.