1Commando  /  Product  /  Access Map
Knowledge graph

Every identity and everything it can reach, on one map.

Every identity, group, role, and resource in your company becomes a node. Every membership and grant becomes an edge that carries the permission, the date it was added, who added it, and when it was last used, wherever the source system records them. Because every identity sits on the same graph, access that looks unlike its neighbors stands out.

OktaIDP
WorkdayHRIS
GitHubCODE
AWSCLOUD
SnowflakeDATA
SlackSAAS
FLAG
Entities
Employees1,960
Contractors124
Service accounts104
AI agents65
Groups and roles389
Resources223
flagged957
Six of the connectors that feed the graph. Counts are from the Marlow Industrial demo org.
How it works
01

Connect

Read-only connectors bring in identities, groups, roles, grants, and sign-in and membership events from your identity provider, HR system, cloud, code, data, and SaaS platforms.

02

Resolve

Group memberships, nested and synced groups, role assignments, and app permissions are followed hop by hop to every resource an identity can reach, including access it was given indirectly.

03

Compare

Each person is compared with peers who share a manager, title, or department, and each machine with others of the same kind and owner. Access that few of them hold is flagged for review.

What you get

Access Map, in practice.

  • One graph across identity provider, HR, cloud, code, data, and SaaS
  • Effective access through nested Okta groups, GitHub teams synced from Okta, and app roles
  • Who granted each piece of access and when, wherever the source records it
  • Raw tables of identities, groups, resources, and grants, with filters and a CSV export
Included · Connectors

Read-only connectors for the systems that hold access.

Identity provider, HR system, cloud, code, data, and SaaS. Every connector reads, and nothing is written back to any system. Okta connects over its API with a read-only token and pulls users, groups, memberships, group rules, and 90 days of sign-in and group membership events, which record who added whom and when. The other systems import from each vendor's standard admin exports, uploaded in the app.

OktaIDP read-only · live API
WorkdayHRIS read-only · export
Google WorkspaceIDP read-only · export
GitHubCode read-only · export
AWSCloud read-only · export
SnowflakeData read-only · export
SalesforceCRM read-only · export
SlackChat read-only · export
Any other appSaaS read-only · CSV
10,826 grants and memberships · 2,084 people · 169 machines · Marlow Industrial demo company
Okta connects over its API, or from its exports. Workday, Google Workspace, GitHub, AWS, Snowflake, Salesforce, and Slack import from each vendor's standard admin exports, and any other app can be added from CSV files in one generic format. Coming next: Microsoft Entra ID, BambooHR, Rippling, GitLab, and Azure, plus live GitHub, AWS, and Google Workspace sync.
01

Connect

For Okta, paste a read-only API token. 1Commando checks it with Okta before saving it and stores it encrypted. For every other system, upload its admin export on the Sources page. Large files upload in parts.

02

Import

Each import rebuilds the graph from every source and matches people across systems by email. Ids stay the same between imports, so review decisions carry over, and every run is kept in the import history.

03

Resolve

Each source's permission model is mapped to the same schema: identities, groups, roles, resources, and the grants between them, with a domain and a sensitivity on every resource.

  • Nine file connectors and a live Okta connector
  • A generic CSV format for any other app: resources, roles, role grants, assignments, and direct grants
  • Nothing is written back to any connected system
  • An Okta token you can remove from 1Commando, or revoke in Okta, at any time
Get started

See your own access graph.

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