AdminPeople, agents and access, managed in one place
Run your organization from one place
Manage people and agents in one roster, give access through groups and access levels, and set the rules every agent in your organization follows.
Members
Invite people| Name | Role | Workspaces | Joined | |
|---|---|---|---|---|
| Maya Okafor | maya@brindle.com | Owner | 3 | Mar 4 |
| Priya Natarajan | priya@brindle.com | Admin | 2 | Mar 4 |
| Marco Vitale | marco@brindle.com | Member | 2 | Apr 18 |
| Sofia BergInvited | sofia@brindle.com | Member | 2 | Sep 22 |
| ScoutAgent | Agent | Member | 2 | May 2 |
| LedgerAgent | Agent | Member | 1 | Jun 11 |
Members
Invite people| Name | Role |
|---|---|
| Maya Okafor | Owner |
| Priya Natarajan | Admin |
| Marco Vitale | Member |
| Sofia BergInvited | Member |
| ScoutAgent | Member |
| LedgerAgent | Member |
See people and agents together
One roster lists every person and every agent in the organization, with their role and workspaces.
Members
Invite people| Name | Role | Workspaces | Joined | |
|---|---|---|---|---|
| Maya Okafor | maya@brindle.com | Owner | 3 | Mar 4 |
| Priya Natarajan | priya@brindle.com | Admin | 2 | Mar 4 |
| Marco Vitale | marco@brindle.com | Member | 2 | Apr 18 |
| Sofia BergInvited | sofia@brindle.com | Member | 2 | Sep 22 |
| ScoutAgent | Agent | Member | 2 | May 2 |
| LedgerAgent | Agent | Member | 1 | Jun 11 |
Give access through groups
Give a group access once, and everyone in it has it, as people join and leave the group.
Members
Create groupDecide what each level may do
Name access levels for each workspace, such as Reviewer or Analyst, and choose what each one allows.
Member
OrganizationBuilt-inCan use agents and create workspaces
Not included on this level
Can do in this organization
Organization levels are built in and can't be edited. To change what people can do, edit the workspace levels above.
Manage people and agents together
Agents are members of your organization, listed and governed beside the people they work with.
Members
Invite people| Name | Role | Workspaces | Joined | |
|---|---|---|---|---|
| Maya Okafor | maya@brindle.com | Owner | 3 | Mar 4 |
| Priya Natarajan | priya@brindle.com | Admin | 2 | Mar 4 |
| Marco Vitale | marco@brindle.com | Member | 2 | Apr 18 |
| Sofia BergInvited | sofia@brindle.com | Member | 2 | Sep 22 |
| ScoutAgent | Agent | Member | 2 | May 2 |
| LedgerAgent | Agent | Member | 1 | Jun 11 |
Members
Invite people| Name | Role |
|---|---|
| Maya Okafor | Owner |
| Priya Natarajan | Admin |
| Marco Vitale | Member |
| Sofia BergInvited | Member |
| ScoutAgent | Member |
| LedgerAgent | Member |
Give access the way your company works
Access follows groups and named levels, so it stays right as people join, move and leave.
Members
Create groupMembers
Create groupSet the rules every agent follows
The settings you choose apply to every agent in the organization, from the first task.
Members
Invite people| Name | Role | Workspaces | Joined | |
|---|---|---|---|---|
| Maya Okafor | maya@brindle.com | Owner | 3 | Mar 4 |
| Priya Natarajan | priya@brindle.com | Admin | 2 | Mar 4 |
| Marco Vitale | marco@brindle.com | Member | 2 | Apr 18 |
| Sofia BergInvited | sofia@brindle.com | Member | 2 | Sep 22 |
| ScoutAgent | Agent | Member | 2 | May 2 |
| LedgerAgent | Agent | Member | 1 | Jun 11 |
Members
Invite people| Name | Role |
|---|---|
| Maya Okafor | Owner |
| Priya Natarajan | Admin |
| Marco Vitale | Member |
| Sofia BergInvited | Member |
| ScoutAgent | Member |
| LedgerAgent | Member |
Secure by default
Admin settings need the Admin or Owner role, and what agents do under them lands in the audit log.
Secrets
New secretKeys your agents and applets can use to call third-party APIs. Encrypted on save, sent only to the hosts you allow, never shown again.
- FactSet API (production)Organization · Bearer · api.factset.com
- Visibility
- Organization · Any applet in the org can be bound to it
- Auth
- Bearer
Allowed hostsThe key may only ever be sent to these hosts, a bare public hostname, e.g. api.stripe.com.api.factset.comAny hostLet the key be sent to any public host, instead of pinning it to a specific list. - Bloomberg data licenceOrganization · Header · api.bloomberg.com, dlws.bloomberg.com
- Weather APIWorkspace · Bearer · Any public host
Secrets
New secretKeys your agents and applets can use to call third-party APIs. Encrypted on save, sent only to the hosts you allow, never shown again.
- FactSet API (production)Organization · Bearer · api.factset.com
- Visibility
- Organization · Any applet in the org can be bound to it
- Auth
- Bearer
Allowed hostsThe key may only ever be sent to these hosts, a bare public hostname, e.g. api.stripe.com.api.factset.com - Bloomberg data licenceOrganization · Header · api.bloomberg.com, dlws.bloomberg.com
- Weather APIWorkspace · Bearer · Any public host
Set it once for every app
The roles, groups and rules you set apply in the web app, the phone apps, the desktop app and the terminal.
Members
Invite people| Name | Role | Workspaces | Joined | |
|---|---|---|---|---|
| Maya Okafor | maya@brindle.com | Owner | 3 | Mar 4 |
| Priya Natarajan | priya@brindle.com | Admin | 2 | Mar 4 |
| Marco Vitale | marco@brindle.com | Member | 2 | Apr 18 |
| Sofia BergInvited | sofia@brindle.com | Member | 2 | Sep 22 |
| ScoutAgent | Agent | Member | 2 | May 2 |
| LedgerAgent | Agent | Member | 1 | Jun 11 |
Members
Invite people| Name | Role |
|---|---|
| Maya Okafor | Owner |
| Priya Natarajan | Admin |
| Marco Vitale | Member |
| Sofia BergInvited | Member |
| ScoutAgent | Member |
| LedgerAgent | Member |
Work across the Context platform
Admin sets the rules. These products show what happened under them.
- IdentitySingle sign-on, directory sync and an identity for every agent.
- Audit logAgent actions and the decisions on them, with who asked and for whom.
- Usage and billingSpend by workspace, person, agent and model, with monthly limits per person.
- ConnectorsThe apps and services your agents may call, tool by tool.
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Deploy in your environment
Run Context in your own cloud, with people coming from your own identity provider.
- Your clusterContext runs on your own Kubernetes cluster, on Amazon EKS or Azure AKS.
- Your directoryProvision and remove people with SCIM, so the roster follows your directory.
- Air-gapped installationInstall without internet access, with the air-gapped installation tested in CI.
- Your identity providerSign people in with SAML or OIDC.
Context runs in production at Qualcomm. Read the case study
- Amazon EKS
- Azure AKS
- Air-gapped
Admin settings are included in every Context organization, including the Free plan.
- Free$0Includes Admin
- Plus$20Per person per month
- EnterpriseCustomEnterprise deployments run in your own cloud.Talk to us about a plan
Questions
Are agents members of the organization?
Yes. Agents appear in the same roster as people, and you give them access the same way.
Which roles are there?
Owner, Admin and Member for the organization. Each workspace can add its own named access levels on top.
Do people come from our directory?
Yes. SCIM adds and removes people as your directory changes, and each new person joins as a member. Groups are made and managed in Context.
Can we give every agent the same instructions?
Yes. Default instructions stack: the organization's first, then the workspace's, then the agent's own.
Who can reach our private network?
Only agents you allow. Organization-wide access is off by default, and an admin must turn it on.
Can we check apps before they are published?
Yes. Add a hook that runs your own security tooling on every publish. In required mode, each publish waits for the scanner's verdict.



