Understanding the structure of tenants and teams in Tines is essential for building a scalable, secure automation program. This organizational framework determines who can access what and how your automation assets are managed.
Tines' tenant and team structure provides:
Clear boundaries between different automation domains
Appropriate access controls for sensitive workflows and credentials
The ability to share resources selectively across teams
A foundation for scaling your automation program as it grows
Understanding the Hierarchy
Tenants are your organization's Tines instance that are created when you purchase a Tines plan or sign up for the community edition.
Teams are workspaces within your tenant where specific groups collaborate.
Each team has its own:
Members with defined roles (Admin, Editor, Viewer)
Stories (workflows)
Resources and credentials
Access controls
Best Practices for Tenant and Team Organization
To build an effective automation ecosystem:
Structure teams around functional areas: Create teams based on departments or functions rather than projects.
Use roles strategically: Assign team roles based on what members need to do - not everyone needs admin access.
Share resources thoughtfully: Make common resources available across teams while keeping sensitive credentials restricted.
Plan for growth: Design your team structure to accommodate your organization's future needs.
By thoughtfully designing your tenant and team structure, you create an automation environment where collaboration is enabled while maintaining appropriate security boundaries.