Skip to main content

Create Teams and Assign Users

Teams control how users work with shared resources. In Siesta AI, teams are managed in Teams, users are managed in Users, and role permissions are managed in Roles.

Team Design​

Create teams around access boundaries, not only the company org chart. A department can have multiple teams if different groups need different tools or data. A project team can include users from several departments if they share the same operational goal.

Good team examples:

  • Sales operations
  • Customer support
  • Finance reporting
  • Executive assistants
  • Client-specific delivery teams

Create a Team​

  1. Open Teams.
  2. Click Add Team.
  3. Fill in Name and optional Description.
  4. Add users in the Users search field.
  5. Click Submit.

Use names that make access easy to understand later, such as Marketing - Production, Finance - Reporting, or Client A - Support.

User Assignment​

Add users only to the teams they need. If a user works across several functions, assign them to multiple teams rather than expanding one team for everyone.

Review team membership regularly, especially after role changes, project completion, or employee offboarding.

Create and Review Users​

In Users, admins can create users and assign roles. The user creation form includes First Name, Last Name, Email, Phone Number, and Password. Role assignment supports Owner, Administrator, and User.

Use Owner only for organization-level ownership, Administrator for operational admins, and User for normal product users. If custom role permissions are used, review them in Roles, where permissions are grouped by areas such as Users, Roles, Agents, and Feedback.

Identity-Based Onboarding​

Admins can choose whether users are invited manually, synchronized from Microsoft Entra ID, or associated with the organization through approved email domains. Domain-based onboarding can support multiple domains, which is useful for organizations that operate under more than one company domain.

Ask Siesta AI technical support to help plan Microsoft Entra ID synchronization or domain-based organization linking. These settings affect access and user lifecycle, so they should be configured deliberately before broad rollout.

Practical Checks​

  • Confirm every team has a clear owner.
  • Confirm each team has only the connections and agents it needs.
  • Confirm whether users should come from manual invitations, Microsoft Entra ID synchronization, or approved domains.
  • Confirm role assignment before users receive access to production agents.
  • Invite pilot users before inviting a full department.
  • Remove test users and temporary access after rollout.