Workspace settings and metrics
Most of what a workspace holds has its own page — members, glossary and QA rules, translation memory, integrations, billing. What is left is gathered here.
Settings
Section titled “Settings”Workspace → Settings carries the name and, read-only, the billing currency chosen when the workspace was created. The currency decides which payment providers are offered, which is why it does not change afterwards; a workspace that needs a different one is a new workspace.
Deleting a workspace needs workspace:delete, which only the owner holds by default, and takes its projects, files and translations with it.
Notifications
Section titled “Notifications”Ownlate notifies people about the things they are involved in, through two channels:
- In-app — the bell in the header, with an unread count. Everything goes here.
- Email — kept for what is addressed to you personally. In a busy workspace, mailing every reviewer about every submitted translation would make the mailbox useless, so
translation.submittedis in-app only.
| Event | When it fires |
|---|---|
translation.submitted | A translation was sent for review |
translation.reviewed | A reviewer marked one reviewed |
translation.approved | A translation was approved |
translation.rejected | A translation was rejected |
comment.created | Somebody commented on a segment |
comment.mentioned | Somebody mentioned you in a comment |
task.assigned | A task was assigned to you |
task.status-changed | A task you are involved in moved |
member.added | Somebody joined the workspace |
suggestion.created | Somebody suggested a translation on an open project |
suggestion.reviewed | Your suggestion was accepted or declined |
Profile → Notifications lets you turn each event on or off per channel. Some events cannot be switched off, because they are how you learn that something is waiting for you.
Notifications are delivered once per recipient per channel, and a redelivered event does not produce a second one.
Metrics
Section titled “Metrics”Workspace → Metrics answers three questions.
How much is happening
Section titled “How much is happening”Activity by day across the workspace, and per project: how many segments there are, how much was written and when. The same view exists at project level under Analytics, with a breakdown by file, so you can see which file is holding up a language.
Who is doing it
Section titled “Who is doing it”Per member: segments translated, approved and rejected, words translated, days active, and the last time they touched anything. This is the honest picture of where capacity is, and where a language has quietly been left to one person.
What the machine did
Section titled “What the machine did”Segments auto-translated, characters spent and an estimated cost — see AI translation.
Languages
Section titled “Languages”The language catalogue is platform-wide: codes with a name and a native name, which is what a project’s source and target languages are chosen from. Projects use BCP 47 codes, so pt-BR and pt-PT are separate languages rather than one with a variant.
Word usage
Section titled “Word usage”Your plan is metered in words, and the counter moves as translations are written. If it ever looks wrong — after a bulk import, say — sync word usage recomputes the workspace total from its approved translations. See Plans and billing.