CloudTeams › Features › Security and control

Security and control

You stay in control. Your data stays yours.

Decide who sees what, see what changed, export everything as CSV, and take a one-click backup.

Book a demoHow it works

No per-seat enterprise pricing.

Admin and control

  • Roles and permissions
  • Sign in with Google, Microsoft or GitHub
  • Allowed sign-in domains
  • Session length
  • Activity log
  • Agents approve before acting
  • Telegram bot allow-list
  • CSV exports
  • One-click backup

In short

CloudTeams gives admins control over access and data. Roles and permissions set what each person can do by area, admins choose allowed sign-in domains and session length, every write goes in an audit log you can export as CSV, AI agents and the Telegram bot only act after a person approves, and your data can be exported as CSV or backed up in one click, with nightly backups and database time-travel behind it. CloudTeams runs on Cloudflare's global network.

AccessRoles and permissions by area
RecordA full activity log of what changed
OwnershipCSV exports and one-click backup

Works with Contractor portal, AI in CloudTeams, Deliver. Last updated October 11, 2026.

The problem

What gets in the way today.

Everyone sees everything

Sensitive rates and deals are open to the whole team.

Nobody knows what changed

A number moved, and no one can say who moved it.

Your data is hard to leave with

Exports and backups are an afterthought.

What you get

A closer look at Security and control.

Sign-in

Sign in with Google, Microsoft or GitHub.

Use the account you already have. No new password to remember.

  • Google, Microsoft and GitHub sign-in.
  • CloudTeams never sees your passwords.
  • Microsoft and GitHub accounts are linked by the provider's unique account ID, so a changed email address or username cannot take over an account. Google accounts are matched by their verified email address.
  • An admin decides who is let in, and contractors sign in the same way.
  • Allowed sign-in domains and session length are set by admins.

Sign-in

  • Google accounts
  • Microsoft accounts
  • GitHub accounts
  • No passwords stored by CloudTeams
  • Admins decide who is let in
Access

The right people see the right things.

Control access by area, and decide how people sign in.

  • Roles and permissions by area: None, View or Edit.
  • Built-in roles, and your own custom roles.
  • Allowed sign-in domains and session length.
  • Contractors log in separately and see only their own data.

Who can do what

  • Roles and permissions by area
  • Custom roles
  • Sign in with Google, Microsoft or GitHub
  • Allowed sign-in domains
  • Session length
Records

See what changed, and take your data with you.

A record you can check, and data you own.

  • A full activity log.
  • CSV exports.
  • A one-click backup, plus nightly backups and database time-travel.
  • The Telegram bot works only for allow-listed accounts, and AI agents draft while a person approves.

Your data

  • Full activity log
  • CSV exports
  • One-click backup
  • Telegram bot allow-list
  • Agents approve before acting
Setup

Make it fit your firm.

Admins shape CloudTeams to how you work.

  • Editable pipeline stages and custom fields.
  • Billing defaults, quiet days and notification defaults.
  • Your logo and color.
  • A Knowledge base of guides for your team.
  • Installs as an app with Web Push alerts, and runs on Cloudflare's global network.

Admin settings

  • Pipeline stages
  • Custom fields
  • Billing defaults
  • Quiet days
  • Notification defaults
  • Brand logo and color
  • Knowledge base
AI controls

AI that stays inside your limits.

The optional AI features are controlled from Admin.

  • Connect your own Anthropic or OpenAI key.
  • Pick the model.
  • Set a monthly spend cap, and pause AI when it is reached.
  • See every AI call counted, with spend and tokens by feature and model.

Admin → AI usage

  • Your Anthropic or OpenAI key
  • Model choice
  • Monthly cap
  • Pause at the cap
  • Usage tracking

How it works

Three steps, no fuss.

  1. 1

    Set the roles

    Choose what each role can do, area by area.

  2. 2

    Set the sign-in rules

    Pick allowed domains and a session length.

  3. 3

    Check and export

    Review the activity log, export CSV, or take a backup.

Keep exploring

More from CloudTeams.

Contractor portalA separate login for contractorsLearn moreAI in CloudTeamsBuilt in, optional and capped by youLearn moreDeliverProjects, time and billingLearn more

FAQ

Questions, answered.

How does CloudTeams control access?

Roles and permissions set what each person can do by area. Admins also choose allowed sign-in domains and session length, and people sign in with Google, Microsoft or GitHub.

Is there an audit log?

Yes. Every write is recorded in an audit log, and it can be exported as CSV.

Can I export my data?

Yes. You can export CSV files and take a one-click backup.

Can the Telegram bot or the AI agents act on their own?

No. The Telegram bot works only for allow-listed accounts, and nothing sends or writes without a button tap in a message the bot just sent to that person. AI agents draft and a person approves.

How do I sign in?

Sign in with your Google, Microsoft or GitHub account. CloudTeams never sees your password. An admin adds your email first, then you sign in with an account that uses it. With GitHub, the primary email on the account must be verified. Contractors sign in the same way, with the email on their Talent record.

Do you support single sign-on?

Sign-in with Google, Microsoft and GitHub is supported. Enterprise SAML SSO is not available yet.

Where does CloudTeams run?

On Cloudflare's global network.

See it on your own data.

Book a time and we will show you Security and control on your own kind of work.

Book a demo