Skip to content

Administer

Access control

Manage permissions through Settings > Access Control. Its Sources, Teams, and Users views let administrators review access from the source or the people who need it.

People and teams

Grant access to the repositories a person or team needs. Review the permissions shown for each source and distinguish the ability to read code from the ability to administer its settings.

Teams help manage shared source grants. Manage people and roles covers invitations and identity provisioning.

Investigation agents and machine identities

Each investigation agent uses a machine credential that limits the codebases it can access. Anyone with access to that agent can investigate against those codebases. Review the machine’s source grants directly or through its team membership.

The connected Jira projects define the ticket context available to the investigation. Configure those projects under Settings > Integrations > Jira Cloud > Project Scopes.

Use API access to manage machine credentials.

Documentation connections

The credentials configured under Settings > Integrations > Agent connections determine which documents the agent can read. Scope those accounts to the spaces and pages needed for investigations.

Check access with a known question and open the cited source. If Driver cannot read a required repository, Jira project, or document, review the corresponding identity and connection rather than assuming another user’s access applies to the agent.

Private continuations

An automated Jira investigation is the shared starting point. Each person’s continuation with Driver is private. Copy information that teammates need into the Jira ticket through your normal workflow.