sinraTeams in Sinra
A team is a group of users who work together. Users belong to exactly one team per organization. This constraint keeps workload calculations clean: there is no double-counting of capacity when a developer appears in two teams.
Creating a Team
- Go to Teams
- Click New Team
- Give the team a name (Backend, Frontend, QA, etc.)
- Add members
Each team gets an auto-generated avatar based on its name.
Roles
Four roles are available per organization:
| Role | Capabilities |
|---|---|
| Developer | Create and update issues, log time |
| Reporter | Create issues, create testings, comment |
| Manager | Everything above, plus manage releases and cycles |
| Admin | Full organization access including billing and settings |
Assign the lowest role that gives each member what they need. Reporters who do not write code should not have Developer access.
Developer Types
Developers have a sub-type that affects workload grouping:
- Backend
- Frontend
- Fullstack
Cycle workload views group by developer type, so you can see backend vs frontend load separately.
Availability Rates
This is the most important configuration in Sinra. Every capacity calculation depends on it.
Set each member’s target_capacity to reflect their actual availability for this project:
| Situation | Rate |
|---|---|
| Full-time, no other projects | 80-100% |
| Part-time or split projects | 40-60% |
| Occasional contributor | 20-30% |
Do not set rates optimistically. If someone is genuinely at 80% but you set them at 100%, every cycle will appear under capacity until you see overruns at delivery.
Updating Rates Mid-Project
If a team member changes their availability (starting a new parallel project, going on leave, returning from leave), update their rate in team settings. Sinra recalculates future cycle capacity immediately. Past cycles keep their historical data.
Setting the Time Zone
When you set up the organization, check its time zone in the organization settings (Europe/Paris by default). Everyone who has not picked a personal time zone sees times in it, including in emails. Members can still choose their own in their profile.
Seat Limits
The number of members you can add depends on your subscription plan. Sinra shows remaining available seats in the team settings. Contact support if you need to increase your seat count.
Inviting Members
Members receive an email invitation when added to a team. They must accept the invitation and create their account before they appear as assignable users in issues and cycles.
Inviting people
Only administrators can invite. You can invite as many people as your subscription has seats; with no seat left, the page links to your subscription and a direct request is refused. Resending to a pending invitee does not use a seat. The invitation email names the organization, who invited you and your role. Choose among developer, product, reporter and manager; each role is described on the invitation page.
Until an invitation is accepted, the member list shows Invitation pending instead of Active, with Resend (a new email and a new link; the old link stops working) and Revoke (withdraws the invitation). An invalid or already used link leads to the sign-in page with a message. Signing up with an address that already has an account shows the same confirmation as a new one and sends that address an email saying so.
When you invite a developer you choose their team; managers, product owners and reporters join no team and weigh on no capacity. An issue created in a refinement session goes to a team (required when there are several), the developers then take the tasks among themselves during the sprint. The platform is chosen separately, never deduced from the team: two teams can work on the same platform.