Organizations And Roles
Understand how Bilbis organizations, memberships, and roles control access.
What this means
An organization is where your team uses Bilbis. It contains members, provider credentials, products, repositories, pipelines, billing, analytics, and audit history.
Each person joins an organization with a role. The role controls which pages they can use and which actions they can take.
When to use it
Read this page when you need to:
- Decide which role to give a teammate.
- Understand why a button is hidden.
- Separate one team's work from another team's work.
- Create a new organization for a different company, team, or environment.
Role overview
| Role | What it is for | Common access |
|---|---|---|
| Owner | The highest organization role. Use for the person responsible for the organization. | Organization control, admin actions, billing-sensitive operations, member management. |
| Admin | Operational administrator. Use for people who configure Bilbis. | Integrations, products, repositories, members, groups, audit-sensitive setup. |
| Developer | Daily user who creates and reviews work. | Pipelines, MRs/PRs, relevant products and repositories. |
| Viewer | Read-only or low-risk access. | View available organization information without managing setup. |
The backend enforces permissions. The UI also hides many actions from users who do not have the required role.
Admin-level actions
Owner and admin users can usually manage:
- Provider credentials.
- Products and repositories.
- Jira and webhook setup.
- Members.
- Groups.
- Audit-sensitive organization settings.
Some actions may be owner-only or platform-admin-only depending on the backend rule.
Developer and viewer expectations
Developers and viewers may still see setup status, pipeline history, or other organization context. If they cannot click a button, the most common reason is that the action changes organization-wide configuration.
For example, a developer may be able to create a pipeline, but they may not be able to add a GitHub credential or invite a teammate.
Organization boundaries
Organizations are separate from each other. Switching organizations changes:
- Which products and repositories you see.
- Which credentials are available.
- Which pipelines, templates, MRs/PRs, learnings, and analytics are shown.
- Which role you have.
You can have different roles in different organizations.
Problems and fixes
| Problem | What to check |
|---|---|
| A user cannot see an admin button | Check their role. Admin or owner access is usually required. |
| A user sees the wrong products | Confirm they are in the correct organization and, if groups are used, the correct group. |
| A user needs access to another organization | Invite them to that organization or ask them to accept a pending invite. |
| A user has the wrong role | An owner or admin can change assignable roles from the Members page. |