Members and projects¶
Organisation admins manage who can access an organisation and which OpenStack projects OpenWatch reads. These tasks live in the admin panel, under Members and Projects.
This page covers organisation-level administration. It is separate from the site-wide super-admin console, which is only used by the operators of an OpenWatch deployment and is not covered in the end-user documentation.
Who can manage an organisation¶
Every organisation has two member roles:
| Role | Can do |
|---|---|
| admin | Everything a member can, plus manage members, projects, notification channels, SMTP, SSO, and view the audit log. |
| member | View dashboards, the resource explorer, alerts and optimisation data for the organisation. |
You need the admin role in an organisation to see the admin panel for it. If you belong to several organisations, use the org selector in the admin sidebar to switch between them.
Managing members¶
Open Admin > Members to see everyone in the organisation with their role and status.
Add a member¶
- Go to Admin > Members.
- Enter the person's email address and choose a role (admin or member).
- Send the invitation.
The invitee receives an email and joins the organisation once they accept. New users are guided through account creation on first sign-in.
Transactional email must be configured
Invitations are sent through the deployment's transactional email relay. On the hosted SaaS this is already set up. On a self-hosted instance, the operator configures it (see Configuration).
Change a role or remove a member¶
- Change role: switch a member between admin and member from the same page.
- Remove: removing a member revokes their access to the organisation immediately. Their account is not deleted; only their membership is removed.
You cannot remove the last admin
An organisation must always keep at least one admin. Promote another member to admin before removing or demoting the final one.
Member limits¶
The number of members an organisation can have depends on its plan. When you reach the limit, add-member actions are blocked until you free a seat or upgrade. See Editions and plan limits.
Managing projects¶
An OpenStack project is the connection OpenWatch uses to read your usage and cost data. Open Admin > Projects to manage them.
Add or edit a project¶
Adding a project means providing the OpenStack credentials OpenWatch uses to query the cloud. The full walkthrough, including where to find each value and how to test the connection, is in Connect your cloud.
From Admin > Projects you can:
- Add a new project and run a connection test before saving.
- Edit an existing project's credentials or display name.
- Remove a project you no longer want to track.
Credentials are encrypted at rest
The OpenStack password you enter is encrypted before it is stored and is only ever used to call the provider APIs. OpenWatch reads your data by default; it changes a resource only when you explicitly trigger an optimisation action (deleting an orphan, or applying a rightsizing change) and confirm it.
Test a connection¶
Use the connection test after adding or editing a project. A successful test confirms the credentials, the authentication URL and the project scope are correct, so cost data can be fetched.
Remove a project¶
Removing a project stops OpenWatch from tracking it and clears its cached cost data. Historical snapshots already captured may remain until they age out. Removing a project in OpenWatch has no effect on the resources in your cloud.
Project limits¶
The number of projects an organisation can track depends on its plan. See Editions and plan limits.
Related pages¶
- Connect your cloud - step-by-step project setup.
- Single sign-on (SSO) - let members sign in with your identity provider.
- Audit log - review member and project changes.