Members
Invite teammates, change roles, deactivate access, and reset member passwords.
What this means
Members are the people who can access an organization.
The Members page shows everyone with access to the current organization, their role, whether their account is active, and recent login context when available.
When to use it
Use the Members page when you need to:
- Invite a teammate.
- Change a member's role.
- Deactivate or reactivate a member.
- Remove someone from the organization.
- Reset a member's password.
- Check whether an invite is still pending.
Before you start
You need owner or admin access to manage members. Bilbis hides member management actions from lower roles, and the backend enforces the same rule.
The owner role is reserved and cannot be assigned from the normal invite or role picker.
Invite fields
| Field | What it means | Default |
|---|---|---|
| Name | Display name for the invited user. | Required |
| Username | Unique username. Allows letters, numbers, dot, underscore, and dash. | Required |
| Email address for sending the invite. If blank, Bilbis shows a shareable invite URL. | Optional | |
| Role | Access level for the invited member. | Developer |
Assignable invite roles are Admin, Developer, and Viewer.
Steps: invite a teammate
- Open Members.
- Select Invite member.
- Enter the person's name.
- Enter a username.
- Add an email address, or leave email blank if you want to copy the invite URL manually.
- Choose a role.
- Send the invite.
If Bilbis returns an invite URL, copy it and send it to the teammate. The link is single-use and lets the teammate set their password and join.
Member actions
| Action | What it does |
|---|---|
| Change role | Updates a member's role to admin, developer, or viewer. |
| Deactivate | Keeps the member row but disables access. |
| Reactivate | Restores access for a deactivated member. |
| Reset password | Creates a password reset flow for that member. |
| Remove | Removes the member from the organization. Their account can still exist elsewhere. |
What happens next
Invited users appear as pending until they accept. Active members can use the organization according to their role and any group access rules.
Removing a member removes their access to that organization, but existing pipeline history stays intact.
Problems and fixes
| Problem | What to check |
|---|---|
| Invite fails with username conflict | Choose a different username. |
| Invite says member already exists | The user may already belong to the organization. |
| User did not get an email | Create the invite without email and share the generated invite URL manually. |
| Role cannot be changed | Owner is reserved and immutable in the normal member UI. |
| User loses product access unexpectedly | Check group membership if groups are used. |