Elaine instances, tenants, users, and roles

Understand Elaine instances and tenant separation, and learn how users, roles, and permissions control access.

Key concepts

 
• An Elaine instance is the Elaine environment operated for a customer.
 
• Tenants provide administrative and data separation for organizational units, brands, markets, or operating models within an instance.
 
• Users represent named human operators; dedicated API identities represent machine integrations.
 
• Roles and permissions control access to functions, data, groups, and administrative actions.

How it works

 
1. Define the required organizational separation and ownership model.
 
2. Create users or integration identities for one accountable purpose.
 
3. Assign the smallest appropriate roles, groups, and functional permissions.
 
4. Test allowed and denied workflows with representative accounts.
 
5. Review access periodically and remove it promptly when responsibilities change.

Governance and considerations

 
• Do not share user or API credentials.
 
• Separate administration, content creation, approval, and integration responsibilities where required.
 
• Document exceptional access and time-limit it when possible.

Note

Exact UI labels, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.

Related topics

 
• Smart Workspace in Elaine.io
 
• Roles and permissions reference
 
• Authentication, network security, and VPN
 
• Privacy by design and by default in Elaine