Skip to main content

Organizations & Teams

Organizations let you collaborate with teammates under a single billing account. Every PromptGuard user starts with a personal organization. You can create additional team organizations, invite members, and control access with role-based permissions.

Concepts

Roles & Permissions

Getting Started

Create a Team

  1. Go to Organization → Team
  2. Click “Create Team”
  3. Enter a team name
  4. Your new organization appears alongside your personal organization

Invite Members

  1. Navigate to Organization → Team
  2. Under Invitations, enter the email address and select a role
  3. Click Send Invitation
  4. The dialog that follows shows the invitation’s accept link. Copy it now if you want to send it yourself: it is shown this once, and never again, not even on a resend
What the invitation does next:
  • “We emailed” means our mail provider accepted the message, not that it arrived. A typo’d address, a spam filter or a full mailbox all look the same from here. In the pending list an invitation shows Sent with a date once the mail provider has accepted it, or Never delivered if it did not. When the email could not be sent at all, the dialog says so and the link is the way to reach them.
  • Only the invited address can accept. The person must sign in with exactly that email address; anyone else who opens the link is told which address it was sent to. So an invitation to a mistyped address cannot be fixed: revoke it and invite the right address.
  • One pending invitation per address. Inviting an address that already has a pending invitation is refused with 409 Conflict. Resend the existing one, or revoke it first.
  • Resend re-mails the same invitation. It uses the same link, and does not extend the expiry.
  • Invitations expire 7 days after they are created, and each one can be used once. To give someone more time, revoke the invitation and invite them again.
The pending list shows each invitation’s expiry date, with Resend and Revoke next to it.

Switch Organizations

Use the organization selector at the top of the dashboard sidebar to switch between your personal organization and team organizations.

Managing Members

Change a Member’s Role

  1. Go to Organization → Team
  2. Find the member in the Members table
  3. Select the new role from the dropdown
  4. Confirm the change

Remove a Member

  1. Go to Organization → Team
  2. Click the remove button next to the member
  3. Confirm removal
Removing a member ends their access immediately and revokes their credentials in this organization: every API key they created here stops working, and every Shadow AI device bound to them is revoked, so its next scan is refused. Keys in their personal organization, and in other organizations they belong to, are untouched. The removal is recorded in the audit log with how many devices and keys were revoked. You cannot remove the owner: transfer ownership first.

Project-level access

Organization roles apply across all projects. For finer-grained control, you can grant a user a role on a single project: useful when a contractor or a partner team should see one project without access to the rest of your organization.
Per-project roles are on every plan, Free included (Pricing).

Project roles

How access is resolved

A user’s effective access to a project is the highest of:
  1. Project ownership: the user who created the project is its owner.
  2. Their organization role: organization Owners and Admins are automatically Admins on every project; organization Members and Viewers carry that role into each project.
  3. Any explicit project role granted below.
Because PromptGuard takes the highest of these, an explicit project role can only raise someone’s access, it never reduces what their organization role already grants. To give someone access to only one project, add them to the organization as a Viewer (minimal org-wide access), then grant them a higher role on the specific project.

Grant a project role

  1. Open the project, then go to its Settings → Access tab
  2. Enter the teammate’s email and choose a project role
  3. Click Add: the change takes effect immediately
To revoke, remove the user from the project’s access list. They retain whatever access their organization role still grants.

Project Members API

These endpoints live under /dashboard/projects/{project_id} and use the session token.
/dashboard/* takes a dashboard sign-in, not an API key. These endpoints are the API the dashboard at app.promptguard.co calls. They are not part of the public API, and no API key or long-lived token works on them. Everything under /api/v1 takes your X-API-Key instead (API reference).To script one anyway, sign in with your email and password. This needs an account that has a password, and an email domain that requires SSO is refused. The access token lasts one hour.
Where an example shows YOUR_SESSION_TOKEN or YOUR_SESSION_COOKIE, it means the access_token from step 1, sent as Authorization: Bearer <token> or as the access_token cookie. A request acts on your personal organization unless it sends X-Organization-Id.

Managed service providers

This section is for the client’s side of the relationship. If you are the provider, the Managed service providers guide walks through running PromptGuard for your clients end to end. A managed service provider (MSP) can manage your organization on your behalf, through a grant: a record that lets the provider’s organization act in yours with one role, such as Admin or Viewer. The provider’s staff never join your organization and never share your logins; they act from their own organization, and every action is theirs in your audit log. A grant follows the same rules as Microsoft’s granular delegated admin privileges (GDAP): the least role that does the job, for a limited time, and only with your agreement.
  • You approve it first. If your organization has an owner, a grant over it starts as Awaiting approval and gives the provider nothing until your owner or an admin approves it. Declining ends it.
  • It can end on a date. A grant may carry an end date. From the end of that day (UTC) the provider can do nothing in your organization, without anyone having to revoke it. Your devices, events and history stay yours.
  • You can see it and end it at any time. Every grant over your organization is listed with its role, start, end date and state.
A client organization that the provider creates for you starts with no owner of its own, so there is nobody to ask: the provider creating it is the agreement, and its grant is active at once. Once the provider invites your first owner, that owner can end the provider’s access like any other client.

Approve, decline or end a provider’s access

  1. Switch to your organization and go to Dashboard > Settings > Team
  2. Under Managed by, each provider shows its role, since when, until when, and its state: Active, Awaiting approval or Expired
  3. Click Approve or Decline on a request, or End access on any other grant
Only an Owner or Admin of your own organization can do this. A provider acting in your organization cannot approve, decline or end anyone’s access, including another provider’s.

Set when a client loses access, for providers

On Dashboard > Clients, each client shows when your access ends. End date sets, moves or clears it.
  • For a client you created, you can set any future date, move it later, or remove it. Setting a later date on an expired grant restores your access.
  • For a client that approved your access, you can bring the date earlier but not later: the client agreed to a window, and more access needs a new grant that the client approves.
Grants that give you nothing right now, because they await the client’s approval or have expired, are listed under Awaiting approval or expired, without the client’s figures.
Ending a provider’s access takes its authority at its next request. It does not revoke enrolment tokens or API keys created in your organization while the provider had access: those belong to your organization. Rotate them as a separate step when a relationship ends.

Ownership

Transfer Ownership

  1. Go to Dashboard > Settings > Team > Danger Zone
  2. Click “Transfer Ownership”
  3. Select the new owner from existing members
  4. Confirm the transfer
After transfer, the previous owner is demoted to admin.

Delete an Organization

  1. Go to Dashboard > Settings > Team > Danger Zone
  2. Click “Delete Organization”
  3. Type the organization name to confirm
Deleting an organization permanently removes all projects, API keys, scan history, and member associations. This cannot be undone. Personal organizations cannot be deleted.

API Reference

The Organizations API is session-authenticated (Dashboard API). All endpoints live under /dashboard/organizations.

List Organizations

Create Organization

Response

Invite a Member

Update Member Role

Remove a Member

Transfer Ownership

Delete Organization

Best Practices

  1. Use the least privilege role — assign Viewer to stakeholders who only need read access
  2. One organization per team — avoid mixing production and personal projects
  3. Rotate ownership proactively — transfer ownership before an owner leaves the company
  4. Audit members regularly — remove inactive members to reduce your attack surface

Next steps

Single sign-on

Sign in through your identity provider with SAML or OIDC

Directory sync (SCIM)

Provision and deprovision members from your IdP

Audit logs

The tamper-evident record of administrative actions
Last modified on November 13, 2026