Using Teams 

The Teams feature of Tines allows for logical separation of users, credentials, resources, and stories. Team members will only be able to access the configuration items of teams that they are a part of unless they are a tenant owner.

Team members can be added using the "Invite" button on the "Members" page of the team. If an account does not exist yet in the tenant when added to a team, an invitation email will be sent to the user to join the tenant. Members can be removed from a team at any point by any team administrator or a tenant owner, unless they are the last member of the Team.

Team Roles 

All members of a team must be assigned one of 3 roles in Tines, Team Admin, Editor or Viewer. Each role has a set of permissions assigned to them which will give read and or write access to objects in the team.

1. Team Admin

This role gives the user unrestricted read and write permissions to all objects in the team. This is useful for admins or team managers responsible to adding/removing users from a team. This will also give them permission to perform destructive actions on a team such such as deleting stories, resources or credentials.

A team admin can change the role of a user or assign a role to a new user on the team members list.

2. Editor

This role gives the user read and write permissions to most objects on the team, but unlike the team admin role, they cannot perform destructive actions on the team such as deleting stories, resources or credentials. For stories with change management enabled, this role will also restrict pushing test changes to the live story (this action is reserved for team admins only).

This role is useful for most users who simply want to create, edit and run stories in Tines.

3. Viewer

This role gives the user read-only permission to most objects on the team.

This role 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.

Permissions table 

Sharing across teams 

Stories, credentials and resources can be shared across teams in order to allow reuse of single credentials, resource information, and complex stories.

Credentials and resources can be shared by using the "Access" configuration options within each individual credential and resources. Sharing is enabled within the team the credential or resource exists in by default, with the option of "All teams & drafts" available to make the item available to all teams within the tenant, or some teams on a per-team basis.

Credentials and resources shared outside the team must each have a unique name when compared to each other team present.

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.

  1. Go to your main menu in the top left corner

  2. Choose Team story allocation from the dropdown

  3. Check the box for the team(s) you want to limit

  4. Set the maximum stories for the team(s)

  5. Click Save

You can always come back and modify these settings.

Was this helpful?