Ejento AI
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Teams
  • Basic Operations
    • Features
      • Organization → Projects → Assistants → Teams Hierarchy
    • Guides
      • Login/Signup
  • Assistants
    • Overview
    • Features
      • Assistant Access Control
      • Assistant Evaluation
      • Evaluation Metrics
      • URL-based Chat Thread Creation and Prepopulation
      • Reasoning Patterns
      • Staging & Publishing
    • Guides
      • Add Assistant
      • Evaluate Assistant
      • Edit Assistant
      • Assistant Edit Access
      • Embed Assistant
      • Delete Assistant
      • Add Favourite Assistants
      • View Assistant Id
      • Voice Calling with Assistants
  • Corpus
    • Overview
    • Features
      • Corpus Permissions
      • PII Redaction
      • ETag Setup for Corpus Incremental Refresh
    • Guides
      • Assistant Corpus Setup
      • Assistant Corpus Settings
      • Corpus Access Control
      • Corpus Connections
      • View Corpus Id
      • View Document Id
      • Tagging
        • Corpus tagging
        • Document tagging
  • Teams
    • Overview
    • Guides
      • Add a Team
      • Edit a Team
      • Delete a Team
      • View Team Id
  • Projects
    • Overview
    • Guides
      • Add a Project
      • Edit a Project
      • Managing Assistants in a Project
      • Delete a Project
      • View Project Id
  • User Settings
    • Overview
    • Features
      • Ejento AI User Access Levels
    • Guides
      • Add new user
      • Invite Users via Link or Email
      • View my User Id
  • API Keys
    • Overview
    • Guides
      • How to generate API Key and Auth Token
  • Workflows
    • Overview
    • Features
      • Workflow Access Control
    • Guides
      • Add Workflow
      • Workflow Chat
      • Workflow Edit Access
  • Tools
    • Overview
    • Guides
      • Tools Overview
      • Create External Tool
      • Connect Tool to Assistant
  • Analytics
    • Overview
    • Guides
      • Analyzing Data in the Analytics Dashboard
  • Chatlogs
    • Overview
    • Guides
      • Managing Chatlogs
      • View Chatlog & Chat thread Id
  • Integrations
    • Overview
    • Guides
      • Email Indexing
      • Microsoft Teams
      • Sharepoint Indexing
      • Google Drive Connector
      • MS Teams Integration Setup
      • Creating a Connection in Credential Manager
      • Slack App
      • Discord Bot
  • Ejento AI Shield
    • Overview
    • Features
      • Understanding Guardrails
    • Guides
      • How to enable Guardrails
  • Assistant Security
    • Overview
    • Features
      • Assistant Red Teaming
    • Guides
      • Red Team an Assistant
  • Permission Sets
    • Overview
    • Guides
      • Add Permission Set
  • Usage
    • Overview
    • Guides
      • Set Spend Limits
  1. Teams

Overview

In Ejento AI, a team is a group of people in your organization who share access. Teams let you manage access in bulk: you give a team access to projects, assistants, or corpora once, and every member gets it. As people join and leave the team, their access follows automatically.

Why teams matter#

As an organization grows, giving access person by person becomes slow and error-prone. Someone always gets missed, and people keep access long after they've changed roles. Teams solve this:
Less admin work. Share a resource with one team instead of dozens of individuals.
Consistent access. Everyone in the team sees the same projects, assistants, and corpora.
Automatic updates. Adding or removing a member updates their access everywhere the team is used.
Safer offboarding. Removing someone from a team removes the access they had through it in one step.
Org-wide permissions. Assign Permission Sets to a team so all members get the same capabilities.

Where teams fit#

Teams sit inside your organization and connect people to resources:
ConceptHow teams use it
ProjectsWhen a team is added to a project, its members get access to that project and its assistants, at the role the team was given (Admin or Member).
AssistantsA team can be given access to individual assistants.
CorporaA team can be given access to a corpus, so members' assistants and searches can use it.
Permission SetsAssigned to a team from Edit Permissions. Every member of the team gets the access these sets grant.
For how access is inherited across the hierarchy, see Organization → Projects → Assistants → Teams Hierarchy.

Team roles#

Everyone in a team has a role:
RoleWhat it means
OwnerThe person who created the team. Has full control, and can't be removed or changed.
AdminManages the team: adds and removes members, changes their roles, and edits team details.
MemberThe default role. Uses everything shared with the team, but can't change the team's settings or members.

Where to find teams#

Teams are managed in Organization settings: click your name at the bottom of the sidebar, choose Organization settings, then open Users & Teams and the Teams tab. The list shows each team's name, owner, creation date, and Permission Sets, with actions to Edit Permissions, edit, or delete it. Click a team's name to see its details and its Team ID.

Use cases#

Department access: Create a "Marketing" team and give it Member access to the "Email Campaign" project. Everyone in Marketing can use the project's assistants, and a new marketer gets the same access the moment you add them to the team.
Content maintainers: Create a "Knowledge Base Editors" team and give it Admin access to the corpora it looks after, so its members can update content without needing access to anything else.
Temporary groups: Create a team for a time-limited piece of work, such as an audit. When the work ends, delete the team, and everyone loses the access they had through it in one step.

Key terms#

Team: A named group of users that can be given access as a unit.
Owner: The team's creator, who always keeps full control.
Team Admin: A member who can manage the team's members and settings.
Team Member: A user who uses what's shared with the team.
Permission Set: An organization-wide bundle of permissions that can be assigned to a team.

FAQs#

Who can create or delete teams?#

Only Global Admins and Application Admins of the organization can create or delete teams. Team Admins can manage a team's members and roles.

Can a person belong to more than one team?#

Yes. Their access adds up across all their teams and anything shared with them directly, and if they have access to something in more than one way, they get the highest level.

What happens to access when a team is deleted?#

Members lose the access they had only through that team. Access given to them directly or through other teams isn't affected. Deleting a team can't be undone.
To create your first team, see Add a Team.
Previous
Teams
Next
Add a Team