Skip to navigation

Team Members & Access Roles

A team member is a person who can sign in to your IBEE organization with their own login. Their access role decides what they can see and do, and, for some roles, which workspaces they can reach. You add people by invitation; they get access once they accept.

Choose a role

RoleGive it toCanCan’t
AdminCo-owners, team leadsEverything: every workspace, billing, team, API tokens, organization details, activity, supportRemove or replace the Owner
TechnicalEngineers who build and run thingsCreate, change and delete resources in all or selected workspaces; open support requests; see activitySee billing, manage the team, create API tokens
CollaboratorPeople who only need to lookView resources and activity in all or selected workspacesCreate, change or delete anything; open support requests
BillingFinance and accountsBilling pages: Summary, Usage, Invoices, Payment Method, Usage Limits; add creditsSee any workspace or resource, activity logs or support

The person who created the organization is its Owner (shown as Primary owner). The Owner always has Admin rights, can’t be removed, and is the only person who can transfer ownership.

What each role can do

CapabilityOwner / AdminTechnicalCollaboratorBilling
View workspaces and resourcesYesYesYes (read-only)No
Create, change and delete resourcesYesYesNoNo
Create workspacesYesOnly if scoped to all workspacesNoNo
Rename workspacesYesNoNoNo
View and manage billingYesNoNoYes
View the team listYesYesYesNo
Invite, remove and resend invitationsYesNoNoNo
View Organization DetailsYesYesYesNo
Edit Organization DetailsYesNoNoNo
View activity logsYesYes, without billing eventsYes, without billing eventsNo
Open support requestsYesYesNoNo
Create API tokensYesNoNoNo

Technical and Collaborator members get either all workspaces (including ones created later) or only the workspaces you select. Admin and Billing are always organization-wide.

How it works

  1. An Owner or Admin sends an invitation to an email address with a role and, for Technical and Collaborator, the workspaces.
  2. The invitee gets an email, signs up or signs in, and clicks Accept.
  3. Access starts at that moment and lasts until an Admin removes them.

Before you begin

  • You must be the Owner or an Admin to invite or remove people.
  • The invitee’s email address. They don’t need an IBEE login yet.
  • Decide the role and workspaces first: a role can’t be edited after the invitation is accepted.

Invite a team member

1

Open Team

Open your organization (its Workspaces page). In the sidebar, under Organization, click Team. The Team Members page opens.

2

Start the invitation

Click Add Team Member.

3

Enter the email

Enter the Email Address. It’s the only required field; the invitee fills in their name when they accept.

4

Choose the access role

Under Access role, choose Admin, Collaborator, Billing or Technical.

5

Choose workspaces (Technical and Collaborator)

Under Workspace access, turn on each workspace the person needs, or click Select all for every workspace, including future ones. At least one is required.

6

Send it

Click Send Invitation. The invitation appears in the table as Invite sent.

An invitation expires after 24 hours. If it does, the row shows Invite expired: click Resend to send a new one, valid for another 24 hours.

Accept an invitation

The invitee:

  1. Gets an email titled “IBEE Portal - Invitation to organization name” with an Accept Invitation link.
  2. Signs up, or signs in if they already have an IBEE login.
  3. On the Organizations page, sees the invitation with who sent it, the role, the workspaces and the expiry date, and clicks Accept (or Decline).

Access starts as soon as they accept. A declined invitation shows Declined; an Admin can delete it or invite again.

Manage team members

The Team Members table shows each person’s Member (name and email), Access Role, Workspace Access, Status and Actions:

  • Workspace Access reads All organization workspaces (Owner and Admins), All workspaces, the names of the selected workspaces, or No workspace access (Billing).
  • Status is Active for members, and Invite sent, Invite expired or Declined for invitations.
  • Technical and Collaborator members can open the page to see who is in the organization, but can’t change anything. Only Admins see pending invitations.

To change someone’s role or workspaces: remove them, then invite them again with the new role and workspaces. Roles can’t be edited in place.

To remove someone: click the trash icon on their row, then confirm in Remove team member. They lose access to the organization and all its workspaces immediately. This can’t be undone; invite them again to restore access.

Members can’t leave an organization by themselves: ask an Admin to remove you.

Transfer ownership

Only the Owner can do this. The new owner must already be an Active member.

1

Start the transfer

On Team Members, click Transfer ownership in your row.

2

Pick the new owner

In Transfer organization ownership, choose the person under New primary owner.

3

Confirm

Type the organization’s name exactly as shown, then click Transfer ownership.

The new owner becomes the Primary owner. You stay in the organization as an Admin. Billing, resources, verification and workspaces stay with the organization. The new owner must have room under their own limit of 3 owned organizations.

Notifications by role

Each role is subscribed to these notification types by default:

RoleDefault notifications
AdminTechnical, Billing, Abuse, Emergency
TechnicalTechnical, Abuse, Emergency
CollaboratorTechnical
BillingBilling

Limits and timing

Value
Invitation valid for24 hours; Resend starts a new 24 hours
Organizations you can join as a member20
Organizations you can own3 (can be raised)
Access after acceptanceImmediate
Access after removalEnds immediately
Roles per member1

Security tips

  • Give each person the lowest role that lets them work: Collaborator to look, Technical to build, Billing for finance.
  • Use selected workspaces to keep contractors out of production.
  • Keep at least two Admins, so the organization isn’t locked if one person is away.
  • Remove people on their last day. API tokens they created stop working once they leave, so create replacements first.

Troubleshooting

You seeWhat it meansWhat to do
”Select at least one workspace”A Technical or Collaborator invitation has no workspaceTurn on at least one workspace, or Select all
Invite expired24 hours passed before acceptanceClick Resend
”This invitation has expired. Please ask the admin to invite you again.” (invitee)The invitee opened an expired linkThe Admin clicks Resend
”Invitation saved, but the email could not be sent. Use Resend on the pending invitation.”The email failedClick Resend
”The selected member must accept their invitation before becoming owner”The new owner hasn’t accepted yetWait until they’re Active
No Add Team Member buttonYou aren’t the Owner or an AdminAsk an Admin
A member can’t see a workspaceTheir invitation didn’t include itRemove and re-invite them with that workspace
The invitee can’t joinThey already belong to 20 organizations they don’t ownThey must be removed from one first