Getting Started › Setting Up
Signing In
CloudM Continuity supports sign-in with either a Google account or a Microsoft 365 account (via Firebase Authentication). This article explains how to sign in for the first time and how the invitation system works.
First-time sign in
- Open CloudM Continuity — Navigate to https://continuity.cloudm.io in your web browser.
- Choose your sign-in method — Click either "Sign in with Google" or "Sign in with Microsoft".
- Select your account — Use the Google or Microsoft 365 account associated with your organisation.
- Grant permissions — On your first sign-in, you may be asked to grant basic profile permissions (name and email). These are used solely for identifying you within the platform.
- You're in — Once authenticated, you will either be taken to your tenant dashboard or prompted to create a new tenant.
Which account should I use?
Use a Google Workspace or Microsoft 365 account from your organisation. Personal accounts (e.g. personal Gmail or Outlook.com) can be used but are not recommended for production environments. Whichever account you use to sign in the first time will be the identity associated with your user profile.
Signing in via invitation
If another admin in your organisation has already set up a tenant, they can invite you to join. Here's how that works:
- You receive an invitation email — The email contains a link to CloudM Continuity.
- Click the link and sign in — Sign in with the Google or Microsoft 365 account that matches the email address the invitation was sent to.
- Accept the invitation — You will be prompted to accept the invitation to the tenant.
- Access the tenant — Once accepted, you will be taken to the tenant dashboard with the role assigned to you by the inviting admin (Super Admin, Admin, or Viewer).
If you already have an account and are invited to an additional tenant, you can switch between tenants using the tenant selector in the sidebar.
User roles
When you sign in, your access is determined by the role assigned to you:
| Role | Permissions |
|---|---|
| Super Admin | Full access. Can manage policies, connections, settings, and invite or remove other users. Can also modify user roles. |
| Admin | Can manage policies and connections. Cannot manage other users or modify roles. |
| Viewer | Read-only access. Can view the dashboard, sync status, and logs, but cannot make any changes. |
Session handling
CloudM Continuity uses Firebase token-based authentication. Key points:
- Sessions are token-based — There is no traditional login/logout session. Your browser holds an authentication token that refreshes automatically.
- Signing out — Use the user menu in the sidebar to sign out. This clears your authentication token.
- Token expiry — If your token expires (for example, after a long period of inactivity), you will be redirected to the sign-in page automatically.
Switching tenants
If you have access to more than one tenant (for example, if you manage multiple customer environments), use the tenant selector at the top of the sidebar. The current tenant name is displayed there — click it to switch between tenants.
Troubleshooting sign-in issues
| Issue | Solution |
|---|---|
| Cannot sign in | Ensure your browser allows pop-ups and third-party cookies for the sign-in domain. Try an incognito window to rule out browser extension conflicts. If using Microsoft sign-in, ensure your M365 admin has not blocked third-party app consent. |
| Signed in but no tenant visible | You may not have been invited to a tenant yet. Ask your organisation's CloudM Continuity admin to send you an invitation. |
| Invitation link not working | Check that you are signed in with the same account (Google or Microsoft) that the invitation was sent to. Invitation links are tied to a specific email address. |
| Wrong role or missing permissions | Contact your tenant's Super Admin to check or update your role. |