When invited to a team, you can then segment users and objects. Objects in Tines include credentials, resources, and workflows (i.e., Stories).
How does it work?
Users can only access the objects within their designated teams. Tenant owners are the only ones who can view all teams and objects across the tenant.
How do I invite users to a team?
Adding members to a team is simple:
Open Tines and click on a team
Click the stacked menu icon
Type their email address
After a team member accepts the invitation, you can configure their role.
Roles in teams include admin, editor, or viewer. Each role within a team is designated certain permissions and levels of access.
This is the editor who also manages the team. They have unrestricted read and write permissions for all objects within the team including:
Add, manage, or remove members of a team
Perform destructive actions such as deleting an object
Push changes to a workflow live through change control
This editor has read and write permissions to most objects across a team, but they cannot manage member access to the team or perform destructive actions.
This role is useful for most users who simply need the ability to create, edit, and run Stories in Tines.
This role gives a user read-only permission across a team. They can view, but not edit, objects in a team.
This role is useful for situations where a colleague or auditor needs oversight or understanding of an automated workflow, without the ability to alter it – or even accidentally break it.
This table provides a detailed view of the exact permissions for the different roles.
Interact with pages
Create new objects
Edit existing objects
Run an action
Import / export a story
Push changes to a story
Manage team members
Object sharing across teams
By default, all objects are shared to the team where it was created. This enables editors to reuse a single object in multiple places. As a result, when an object is changed or updated, that change is reflected everywhere the object is used.
Limiting or increasing access to an object
When creating a credential or resource, the editor defines the access level. They can choose to share it with all teams or select specific teams. This is useful when some teams shouldn't be able to access a credential or resource.
Note: all objects shared outside a team must have a unique name.
More information on Story sharing configuration can be found with the Send to Story configuration options.
Team story allocation
If you have multiple teams in a tenant, the tenant owner can provision story limits by team.
Go to your main menu in the top left corner
Team story allocationfrom the dropdown
Check the box for the team(s) you want to limit
Set the maximum stories for the team(s)
You can always come back and modify these settings.
Please note: depending on your plan, you may only have access to a certain number of teams and builders (editors and team admins). If you need to increase your limits, please reach out to your Customer Success Manager. See the Pricing Explained for more information.