Read
Resolve the users, groups, resources, and policies needed for authorization.
Overview
Inherit identity and group permissions for every run.
- · Vendor-supported OAuth or scoped service credentials
- · Read and write access configured separately
- · Tool calls and outcomes recorded per run
Connector contract
Control what agents can do in Okta.
Exact authentication methods and available scopes depend on your Okta plan and deployment. Context keeps the connector configuration explicit.
Act
Apply changes only through the policy and approval path you configure.
Verify
Record the principal, requested action, authorization, and outcome.
Set up the connection
- 01
Authenticate
Connect Okta with an admin-approved OAuth flow or scoped credential supported by the vendor.
- 02
Choose scope
Select the accounts, workspaces, projects, or resources available to the runbook.
- 03
Map policy
Set read and write permissions, reviewer gates, and the identity used for each action.
- 04
Test a run
Verify one read, one permitted action, and the resulting audit record before rollout.
Build with Okta
Okta can be added to any Context runbook. Start from a prebuilt agent, then choose the resources and actions it needs. Browse all agents →
More in Identity & security
Connect Okta to Context.
Request demo