Skip to content

User Management & Security

This guide covers how primary account holders manage their team in Aliveo AI: inviting users, enabling/disabling access, enforcing two-factor authentication, AI client and Slack settings, directory sync, and the step-up auth flow that protects sensitive actions.

Who can do what? Only primary account holders see the user management surface. Secondary users still get to use the platform—they just don’t administer team membership.


Roles

Aliveo has two user types:

  • Primary user — the account administrator. Connects integrations, sets context, invites secondary users, and controls 2FA enforcement, AI client access, and Slack settings.
  • Secondary user — a teammate added under a primary account. Has access to the same workspaces, chats, dashboards, and automation agents, but cannot manage other users, and cannot push changes to your ad platforms unless granted actioning permissions.

Aliveo can also set up any user, primary or secondary, as read-only. Read-only users can look at chats, dashboards and agent reports, but can't create or change things, manage the team, or push changes to your ad platforms. There's no switch for this in the app; ask your Aliveo contact.

If your workspace is configured with SSO/SAML, your identity provider is the source of truth—team members appear with an SSO badge, and you can’t add, disable or enable users from Aliveo.


Inviting a Team Member

  1. Open My Account → User Management.
  2. Click Add User.
  3. Enter the new user’s email address, first name, and last name (all required), then click Send Invite.
  4. Confirm with a one-time email code as step-up authentication (see below).
  5. The user receives an email with a temporary password and a login link. Until they sign in, their status shows Invited.

Once they sign in, their status flips to Active.

:material-domain-off-outline: On some enterprise deployments, the User Management page is turned off and team membership is managed in the customer’s identity provider instead.


Disabling and Re-enabling Users

Instead of deleting users (which would orphan their chats and saved workflows), Aliveo uses disable / enable controls in the Access column of the team table:

  • Disable access — revoke access immediately. Their chats, dashboards, and shared agents remain available for the rest of the team, but they can no longer sign in.
  • Enable access — restore access. Their previous content is exactly as they left it.

Both actions require a fresh one-time email code (step-up auth). Disabled users carry a Disabled badge in the team table.

The team table also has a Search members box (matching name, email, or status) and a Refresh button to reload the membership list.


Two-Factor Authentication (2FA)

Personal 2FA setup

Any user can turn on TOTP-based 2FA from My Account → Personal account settings:

  1. In the Settings card, turn on the Two Factor Authentication switch.
  2. Scan the QR code with your authenticator app (Google Authenticator, 1Password, Authy, etc.).
  3. Enter the 6-digit code shown by the app to confirm.

From then on, every login requires the 6-digit code in addition to your password. To turn 2FA off, switch it off and enter a current code from your app. If your organization requires 2FA, the switch is locked on and marked Required by your organization.

Org-wide 2FA enforcement

Primary users can require 2FA for every member of the team:

  1. Open My Account → User Management.
  2. In the Security card, turn on Require Two-Factor Authentication for all team members.
  3. Click Require 2FA in the confirmation dialog.
  4. Confirm with the email code.

Once enforcement is on:

  • Users who already have 2FA continue logging in normally.
  • Active users are signed out within an hour. Anyone without 2FA must complete TOTP setup on the Set up Two-Factor Authentication screen at their next login before they can use the app.
  • Nobody can turn off their own 2FA while the policy is on.

The Security card isn’t shown on SSO workspaces, where your identity provider handles sign-in security.


Step-Up Authentication (Email OTP)

Some actions are sensitive enough that a regular login session is not enough. Aliveo asks you to re-authenticate with a one-time email code for these actions, even if you signed in minutes ago.

Step-up auth fires when you:

  • Invite, disable, or enable a user.
  • Change a user’s actioning permissions.
  • Turn org-wide 2FA enforcement on or off.
  • Turn AI client access on or off.
  • Change either Slack setting.
  • Regenerate the SCIM token.
  • Change your password.

The flow is:

  1. You attempt a sensitive action.
  2. A Confirm your identity dialog opens, and we email you a one-time code.
  3. Enter the 6-digit Verification code and click Confirm.
  4. The original action proceeds.

If you cancel the dialog, nothing changes—the action is aborted. If the code doesn’t arrive or expires, click Resend code without re-doing the original action.


AI Client Access (MCP)

The AI client access (MCP) card controls whether your team can use Aliveo from Codex, Claude, and other MCP-compatible AI clients.

  • Turn on Allow team members to connect Aliveo to AI clients to let everyone on your team—primary and secondary users—connect. Each person then sees AI Integrations in their My Account menu, with setup instructions. See Connecting AI Clients.
  • Turn it off to end every connection on your team at once.

Each connection is authorized per user, through a browser sign-in. Changing the setting requires email OTP re-authentication. On some deployments, AI client access is required and the switch can’t be turned off.


Slack Settings

The Slack card has two toggles:

  • Allow Non-Aliveo Users to invoke @Aliveo AI in Slack — when on, anyone in your Slack workspace (not only users with Aliveo accounts) can mention @Aliveo AI to generate insights. When off, only people with Aliveo accounts can use the bot.
  • Allow applying actions from Slack — when on, people can apply recommended ad-platform changes from a Slack reply, but only within their own actioning permissions. Anyone without permission gets an error when they try. When off, applying from Slack is turned off for everyone. Turning it on notifies the account owner.

Both changes require email OTP re-authentication.

These toggles control what your team can do with Slack. Each person connects their own Slack account from Personal account settings → Communication (see below). See Slack Integration for the full Slack setup.


Actioning Permissions

Actioning—pushing changes like budgets, bids, status, and pausing back to your ad platforms—is controlled per user, so you can let specific teammates act while everyone else stays analysis-only.

Who can action by default

  • Primary users can action by default.
  • Secondary users cannot action until you grant them access.
  • Read-only users can never action, even if a grant exists.

Granting a secondary user access

  1. Open My Account → User Management.
  2. In the team table, open Actioning permissions for the user.
  3. Grant access at whatever scope fits:
    • By account type — e.g. every Google Ads account, for a single organization or All organizations.
    • By specific account — individual accounts within an organization.
    • All accounts, all organizations — the broadest grant.
  4. Save. The dialog shows a running summary of exactly what that person will be able to action, so you can confirm before saving.

Grants are additive and scoped per organization: an All organizations grant applies everywhere, while a per-organization grant applies only within that business.

Only primary users can view or change actioning permissions. For what can actually be changed on each platform, see the Actioning guides.


Directory Sync (SCIM)

If your organization provisions users from an identity provider over SCIM, the User Management page also shows a Directory Sync (SCIM) card. It appears only once SCIM has been set up for your organization, and read-only users don’t see it.

The card gives you what your identity provider’s SCIM connector needs:

  • SCIM connector base URL, plus the authentication method, SCIM version, and unique identifier field.
  • Bearer token — click Reveal to see and copy it.
  • Regenerate token — creates a new token and stops the old one working immediately. User sync pauses until you update your identity provider with the new token. You’ll confirm, then verify with an email code.

Personal Account Settings

Each user has their own page (My Account → Personal account settings) with:

  • Personal Details — name, photo, phone number, and company.
  • Settings — the Two Factor Authentication switch, plus API Keys for programmatic access on enterprise plans.
  • Change Password — for non-SSO accounts.
  • Browser Notifications — turn on Notify me when tasks finish to get a desktop notification when a long-running chat, dashboard, or workflow finishes while you’re on another tab. Use Send test notification to check it works.
  • Communication — under Slack Accounts, click Add to Slack to connect your Slack workspace. See Slack Integration.
  • Preferences — your default line of business and the accounts you’re most interested in.

Usage Visibility

The Usage page (My Account → Usage) shows activity in Aliveo—logins, chats, workflows, dashboards, and more:

  • Primary users see a team-wide roll-up with a per-member breakdown.
  • Secondary users see only their own usage.

See Usage for the full breakdown.


Hidden Tenant Hardening

A few enterprise hardening rules you should know exist but won’t see in the UI:

  • Aliveo employee accounts (@aliveo.ai) are hidden from customer admin views unless the primary user is also @aliveo.ai. Customer teams only see their own people.
  • Some areas of the app (e.g. User Management itself, or Slack) can be turned off for a specific enterprise deployment through per-deployment feature flags set at provisioning time.

If your team needs special handling, talk to your Aliveo contact.


Security Notifications

Aliveo emails a security notification to the account owner (and to the affected user) when someone adds, disables, or re-enables a user; changes a password; turns 2FA on or off; changes org-wide 2FA enforcement; regenerates the SCIM token; or changes Slack actioning or AI client access. If you get one for a change you didn’t expect, reach out to your Aliveo contact.


For the encryption, isolation, and compliance posture behind these features, see Security and Privacy.