← Documentation

Organisation and account

The team and its roles, enterprise sign-in, the journal, the organisation's settings and your account.

Last updated: November 1, 2026

Organisation, team and rights

In FinOps Move2Cloud, everything belongs to an organisation: your company, a subsidiary or a client you support. Its cloud accounts, budgets, dashboards and alerts are shared by its members. The same person can belong to several organisations, with a role in each, and switch from one to another in one click.

Organisation settings → Team: inviting a member by choosing their role, and the list of members (role, job title, last activity, status), filterable by role.

Organisation settings → Team: inviting a member by choosing their role, and the list of members (role, job title, last activity, status), filterable by role.
Organisation settings → Team: inviting a member by choosing their role, and the list of members (role, job title, last activity, status), filterable by role.

Shared cloud accounts

Cloud accounts are connected once, for the whole organisation, by its owner or an administrator; the tool only reads. Every member then sees the same figures, up to date after each synchronisation, without handling any key or asking the provider for access.

  • each person chooses their default scope (a provider, some accounts, projects or apps) without changing anything for the others;
  • an account can be hidden for the whole organisation, without deleting its data, then shown again in one click;
  • a member who leaves loses access to the costs, not the organisation: the cloud accounts stay connected.

Roles and rights

With the Standard (2 members, owner included), Pro (5 members) and Enterprise (15 members) plans, plus extra seats at €29 excl. tax per month on Pro and Enterprise, each person invited gets a role, which the owner or an administrator can change at any time (on Standard, editor or viewer: the administrator role comes with Pro):

  • the owner holds the subscription and the invoices, appoints the administrators and can transfer the ownership;
  • an administrator manages the cloud accounts, the synchronisation, the alerts, the editors and the viewers, and reads the activity log;
  • an editor sets the budgets, handles the recommendations and creates dashboards;
  • a viewer views the costs, the budgets, the recommendations and the dashboards shared with them, and exports them.
OwnerAdministratorEditorViewer
View the costs, budgets and recommendations, and export them✓✓✓✓
Open the dashboards shared with them✓✓✓✓
Use Cloud Intel, write to support✓✓✓✓
Create dashboards, share them✓✓✓✗
Set the budgets✓✓✓✗
Move the follow-up of recommendations forward (status, assignee, priority), document a savings measurement✓✓✓✗
Run a synchronisation on demand✓✓✓✗
Approve or verify a recommendation, validate a savings measurement✓✓✗✗
Connect and set the integrations (Jira, Slack, Teams, GitHub, GitLab)✓✓✗✗
Connect, change or remove cloud accounts✓✓✗✗
Set the automatic synchronisation, the alerts and the organisation's profile✓✓✗✗
View the activity log and all support requests✓✓✗✗
Invite, change a role, remove a member✓editors and viewers✗✗
Set up enterprise sign-in (SSO)✓✓✗✗
Appoint an administrator✓✗✗✗
Outgoing webhooks, cost anomaly detection✓✗✗✗
Subscription, invoices and means of payment✓✗✗✗
Transfer ownership, delete the organisation✓✗✗✗

Alerts for the right people

Budget alerts go to the recipients the organisation chooses, up to ten addresses: when the threshold is reached, when the forecast announces an overrun, and when the budget is exceeded. Each member also sets, subject by subject, how they are told: in the application, by e-mail or by a browser notification. A weekly recap sends the team a dashboard's figures, on the day chosen.

Sharing without opening everything

A dashboard stays private until its author shares it: with the whole team, with a few people, or through a read-only public link, valid for 24 hours. The PDF and CSV files generated stay with the person who produced them.

Staying in control

The activity log says who did what: cloud accounts, team, settings, budgets, shares, kept 7 to 30 days as the organisation chooses. Two-factor authentication is mandatory for everyone, the owner chooses the sign-out after inactivity, and with the Enterprise plan your colleagues sign in with your company's Microsoft Entra ID directory (SSO).