Skip to main content

Managing Workspace Members and Permissions

Written by Kadri - RichAPI Support Team

A RichAPI workspace is a team account that holds its own members and API keys. The credit balance belongs to the organization, and all its teams spend from it. Every member holds one role: Owner or Member. The role decides who can invite people, change a role, remove a member, buy credits, and open the billing portal.

What is a RichAPI workspace?

A RichAPI workspace is a team account. The dashboard shows a workspace as a Team. The workspace owns the API keys and the usage history. The organization owns the credit balance, and every team in the organization spends from it. The workspace URL is https://app.richapi.ai/home/<team-slug>.

The member list is the Members tab of the Organization page, at https://app.richapi.ai/home/<team-slug>/organization?tab=members. Select Organization under Account in the sidebar to open it. The tab lists every member of every team in the organization, with a Team column. The old address /home/<team-slug>/members opens the same tab.

The person who creates the workspace becomes its first Owner. A workspace holds one or more Owners and any number of Members.

Which roles exist in a RichAPI workspace?

RichAPI has exactly two roles.

Role

Summary

Owner

Manages the members, the invitations, and the settings of the team.

Member

Uses the team. Holds no management rights.

An Owner outranks a Member. RichAPI does not support a custom workspace role.

An organization owner is a person who holds the Owner role on at least one team in the organization. Some actions need an organization owner, because they change the shared credit balance or the rules for every team.

What can each role do in a RichAPI workspace?

Action

Owner

Member

See the Members tab

Yes

Yes

See pending invitations

Yes

No

Invite a new member

Yes

No

Change the role of a member

Yes

No

Remove a member

Yes

No

Move a member to another team that you own

Yes

No

Change the team name and the team logo

Yes

No

Create, revoke, and delete an API key

Yes

Yes

See usage and the credit balance

Yes

Yes

Buy credits, change auto-reload, and open the billing portal

Yes, as an organization owner

No

Set the monthly spend limit of a team

Yes, as an organization owner

No

Block endpoints for a team

Yes, as an organization owner

No

Rename the organization

Yes, as an organization owner

No

A Member opens the Members tab and sees the member list. The Pending Invites card stays empty for a Member, because only an Owner can read the invitation list.

How to invite a member to a RichAPI workspace

  1. Sign in as an Owner of the workspace.

  2. Select Organization under Account in the sidebar, then open the Members tab.

  3. Select Invite Members.

  4. If you own more than one team, select the team in the Team list.

  5. Enter the email address of the person to invite.

  6. Select Owner or Member in the role list.

  7. To add another address, select Add another one.

  8. Select Send Invites.

RichAPI sends one invitation email per address. Each invitation expires 7 days after RichAPI creates it. One dialog accepts a maximum of five invitations.

CAUTION: Do not enter the same address twice in one dialog. The form rejects the second entry with the message Duplicate emails are not allowed.

The dialog reports each address that RichAPI rejects.

Reason shown

Meaning

User is already a team member

The address already belongs to a member of the workspace.

Invitation already exists

A pending invitation for that address and that workspace already exists.

An Owner manages a pending invitation from the actions menu of the Pending Invites card. The menu holds Update Invitation, Resend Invitation, and Remove Invitation. After the invitation expires, Resend Invitation changes to Renew Invitation. Both actions move the expiry date 7 days into the future.

How to accept a RichAPI workspace invitation

  1. Open the invitation email.

  2. Select the accept link. The link opens https://app.richapi.ai/join/accept?invite_token=<token>.

  3. Read the workspace name, the role, and the expiry date on the page.

  4. If you have no RichAPI account, select Sign Up. If you have an account, select Sign In.

  5. Sign in with the same email address that received the invitation.

  6. Select Accept Invitation.

RichAPI creates the membership, deletes the invitation, and opens the workspace home page.

Status

Meaning

What to do

403

The invitation went to a different email address.

Sign out. Sign in with the address that received the invitation.

404

The invitation does not exist.

Ask an Owner of the workspace to send a new invitation.

410

The invitation expired.

Ask an Owner of the workspace to select Renew Invitation.

How to change the role of a member

  1. Sign in as an Owner of the workspace.

  2. Select Organization under Account in the sidebar, then open the Members tab.

  3. Select the actions menu at the end of the member row. If the person belongs to more than one of your teams, select Manage in and the team name first.

  4. Select Update Role.

  5. Select the new role in the Role list.

  6. Select Update Role to confirm.

Four rules apply to a role change.

  • The actions menu stays hidden on your own row. You cannot change your own role in the dashboard.

  • Only an Owner of the member's team sees the actions menu.

  • An Owner cannot demote another Owner when that team is the other person's only Owner role in the organization. The API returns 403 with the message You cannot demote another owner of this organization. They must hand over ownership themselves, or a system administrator must do it.

  • RichAPI blocks the demotion of the last Owner of a team, with the message Cannot demote the last owner of a team.

How to remove a member from a RichAPI workspace

  1. Sign in as an Owner of the workspace.

  2. Select Organization under Account in the sidebar, then open the Members tab.

  3. Select the actions menu at the end of the member row.

  4. Select Remove from Account.

  5. Select Remove User from Team to confirm.

WARNING: Confirm the member row before you select Remove User from Team. The member loses access to the workspace at once.

Removal deletes the membership row only. The API keys, the credits, and the usage history of the workspace stay in place. A removed person rejoins only through a new invitation.

Rule

Result

The caller is a Member, not an Owner.

The API returns 403 with the message You do not have permission to manage members.

The target is another Owner, and this team is their only Owner role in the organization.

The API returns 403 with the message You cannot remove another owner of this organization. They must hand over ownership themselves, or a system administrator must do it.

The caller targets their own membership.

The API returns 400 with the message Use the leave-team endpoint to remove yourself.

The target is the last Owner of the team.

RichAPI blocks the removal with the message Cannot remove the last owner from a team.

No member removes their own membership from the Members tab. To leave a workspace, ask an Owner of that workspace to remove you. Read Leaving a Workspace and Transferring Ownership for the full procedure.

How to transfer ownership of a RichAPI workspace

The dashboard moves ownership through a role change. Promote the new Owner. The dashboard has no Transfer Ownership action.

  1. Sign in as an Owner of the workspace.

  2. Select Organization under Account in the sidebar, then open the Members tab.

  3. Select the actions menu on the row of the member to promote.

  4. Select Update Role.

  5. Select Owner in the Role list.

  6. Select Update Role to confirm.

A workspace holds more than one Owner at the same time. You cannot step down in the dashboard: your own row has no actions menu, and the new Owner cannot demote you while this team is your only Owner role in the organization. To step down after the promotion, write to [email protected]. For the full handover procedure, read Leaving a Workspace and Transferring Ownership.

WARNING: Promote a member to Owner only after you confirm the identity. An Owner can invite and remove members, change roles, and manage the team settings. An Owner also counts as an organization owner, so they can buy credits and set spend limits.

How do you block endpoints for a team?

Every team can call the public RichAPI endpoints by default. RichAPI grants private endpoints to the organization. An organization owner can block endpoints for one team, and the block applies to every API key of that team.

  1. Sign in as an organization owner.

  2. Select Organization under Account in the sidebar, then open the Teams tab.

  3. In the row of the team, select Manage access in the Endpoint access column.

  4. Select each endpoint to block. Block all and Unblock all change every endpoint at once.

  5. Select Save.

A call to a blocked endpoint returns status 403 with the response {"error": "Endpoint not available on your plan"} and costs no credit.

If the team has negotiated per-endpoint pricing, the dialog shows Managed by support. Write to [email protected] to change the endpoint access of that team.

The Teams tab also holds the Monthly spend limit of each team. Leave the limit blank for no limit. A limit of 0 blocks all spend for that team.

How to list the endpoints your workspace can call

Send a request to GET https://api.richapi.ai/api/v1/my-endpoints with an API key of the workspace. The response lists every endpoint that the workspace can call.

Response field

Type

Description

rate_tier

string

The rate tier of the workspace.

total

integer

The number of entries in endpoints.

endpoints

array

One entry per endpoint that the workspace can call.

endpoints[].name

string

The endpoint name, for example enrich_profile.

endpoints[].pricing

object

The credit price of the endpoint, for example {"credits_per_call": 1}.

endpoints[].status

string

The availability of the endpoint.

endpoints[].category

string

The catalog category of the endpoint.

endpoints[].input_schema

object

The request body that the endpoint accepts.

cURL

curl https://api.richapi.ai/api/v1/my-endpoints   
-H "x-api-key: YOUR_API_KEY"

Python

import requests

response = requests.get(
"https://api.richapi.ai/api/v1/my-endpoints",
headers={"x-api-key": "YOUR_API_KEY"},
timeout=60,
)
response.raise_for_status()
print(response.json())

Node.js

const response = await fetch("https://api.richapi.ai/api/v1/my-endpoints", {
method: "GET",
headers: {
"x-api-key": "YOUR_API_KEY",
},
});

const data = await response.json();
console.log(data);

How do member seats relate to billing?

RichAPI bills a credit for each successful API call. RichAPI charges no fee for a seat. One credit costs $0.02 on the 1,000 and 5,000 credit packs, and less on larger packs.

  • Credits belong to the organization, not to a member. Each team can have its own monthly spend limit, which an organization owner sets on the Teams tab.

  • Every member of the workspace spends from the same credit balance.

  • A new member costs 0 credits.

  • Removal of a member returns 0 credits.

  • Only a successful call spends a credit. A non-2xx response spends no credit.

The next table shows the credit total for a workspace on an endpoint that costs 1 credit per call.

Members

Calls per member per month

Credits per month

Cost per month

1

1,000

1,000

$20.00

5

1,000

5,000

$100.00

10

1,000

10,000

$200.00

Every member can create an API key. Only an organization owner can buy credits, change auto-reload, and open the billing portal.

Frequently asked questions

Which roles exist in a RichAPI workspace?

A RichAPI workspace holds two roles, Owner and Member. RichAPI does not support a custom workspace role.

Can a Member invite another person to the workspace?

No. Only an Owner can invite. The Invite Members button stays hidden for a Member.

How long does a RichAPI invitation stay valid?

An invitation expires 7 days after RichAPI creates it. An Owner selects Renew Invitation on an expired invitation, or Resend Invitation on an active one, to move the expiry date 7 days into the future.

Does a new member increase the RichAPI bill?

No. RichAPI charges no fee per seat and bills credits per successful API call. A workspace with ten members and a workspace with one member pay the same amount for the same call volume.

Can two people own the same RichAPI workspace?

Yes. A workspace holds more than one member with the Owner role. RichAPI blocks the removal or the demotion of the last Owner.

Can I remove myself from a RichAPI workspace?

The dashboard shows no self-service control that leaves a workspace. To leave a workspace, ask an Owner of that workspace to remove you from the Members tab. For the full procedure, read Leaving a Workspace and Transferring Ownership.

Which endpoints can my workspace call?

Send a request to GET https://api.richapi.ai/api/v1/my-endpoints with an API key of the workspace. The response lists every endpoint that the workspace can call, with the price and the status of each one.

Related articles

Did this answer your question?