Customize Sinra for your organization: workflow statuses, labels, categories, and platforms. Everything configures without code from the settings panel.

Overview

Sinra adapts to your process, not the other way around. The Configuration section lets admins define elements shared across the entire organization: workflows, tags, and contexts.

Statuses

Statuses define the stages of your workflows. Sinra distinguishes two status types, and each issue type uses exactly one of them:

Writing statuses: progress of a specification or a plan (e.g. Draft, In Review, Approved)
Development statuses: progress of a task or a bug (e.g. To Do, In Progress, In Testing, Done)

A specification or a plan never has a development status: how far it is built is calculated from its tasks (its realization). A task or a bug never has a writing status. Each status belongs to a group (to do, in progress, done): an issue is considered done when the status of its type is in the done group.

For each status you can set:

Name and emoji for visual identification
Completion percentage for progress calculation
Order via drag-and-drop

Create as many statuses as your process requires. A status set to 100% is treated as terminal.

Labels

Labels are colored tags applied to issues, capabilities, and projects. They serve as free-form categorization: work type, functional priority, business domain, etc.

For each label:

Name and color
Scope: issues only, capabilities, or both

Labels are filterable in the issue list using equals, in, and is empty operators.

Platforms

Platforms indicate the technical context of an issue:

Website
Mobile (iOS / Android)
Backend
Frontend
Infrastructure

Each issue can be tagged with a platform. This allows filtering and visualizing load by technical context, useful for full-stack or multi-product teams.

Notification preferences

Each person sets their own mention emails from the notification preferences page:

Mention notifications: turn the emails on or off. The notification center keeps listing your mentions either way.
Batch window: how long Sinra waits before sending, from 1 to 1440 minutes (15 by default). Mentions received within the window are grouped into one email.

Every mention email also carries an unsubscribe link that turns the emails off in one click. A link from an email sent before the notification center existed shows an “expired link” page that leads to these preferences.

Time zones

Every time in Sinra (comments, meetings, postmortems, emails) is shown in the time zone of the person reading it.

Organization time zone: an admin sets it in the organization settings (Europe/Paris by default). It applies to everyone who has not chosen their own.
Personal time zone: optional, set in your profile. Choose “Organization time zone” to follow the organization again.
Browser suggestion: when your browser is in another time zone, a banner offers to use it once. Accept or decline; it does not come back.
Hover a time to read the full date and the time zone that was applied.

Dates without an hour (the start of a cycle, a release date) never shift. The API and exports always use UTC (Z). “Today” follows the reader’s time zone.

Best Practices

Statuses: keep it simple. 4 to 6 development statuses cover most workflows. Too many statuses creates friction.

Labels: avoid duplicating platforms or categories. Use labels for what does not fit into the other axes.

Categories and platforms: define them once at project kickoff. Changing categories mid-project means re-tagging existing issues.

Roles and the manager dashboard

Each role type has a description shown on the roles list and the invitation page. The manager role follows delivery: its dashboard shows team health, the releases timeline, risks and key metrics, and it gets the same getting-started steps as product.