Workspace and team
Invite teammates, assign roles, enroll in MFA, and manage your profile.
Settings for managing who has access to your Watari workspace and how each person's account is secured.
Inviting teammates
Go to Settings → Team and click Invite.
Enter the invitee's email address and choose their role, Admin or Member. The dialog shows what each role can do.
Click Send invite. The invitee receives an email with a link to accept the invite. The link is valid for 7 days.
If the invitee is new to Watari, they create their account when they click the link. If they already have a Watari account, they sign in and click Accept invitation. Either way, they use the email address the invite was sent to.
If the link opens in a browser already signed in to a different Watari account, the page says which account is signed in and which address the invite is for. Sign out and switch account signs out and opens sign in with that address filled in, then brings them back to the invite to accept it. Stay signed in keeps the current account and goes back to its workspace.
Roles
Watari has three roles: Member, Admin and Owner. Each role can do everything the one before it can, plus its own list. The same list is shown on Settings → Team and in the invite dialog.
Member
- Triage issues and answer Watari's questions
- Start a draft fix and try it again with more detail (never billed)
- Approve and send customer updates
- Read a repository again and send a test message to team chat
- See who owns each folder of the code
Admin: everything a member does, plus
- Connect and disconnect tools
- Add and remove repositories
- Invite people, remove them and change their role
- Choose how Watari works, when the customer hears, and which branches it uses
- Rename the workspace and change its logo
- Ask Watari to search the code again for an issue
- Ask Watari to read a ticket again
- Add a ticket by hand
- Suggest code owners for a repository
- Change the plan, the monthly limit and billing details, and see usage and invoices
Owners and admins also get the notices about the workspace itself: a tool that stopped working, usage and billing.
Owner: everything an admin does, plus (owner only, one owner per workspace)
- Change the payment card
- Cancel the subscription
- Delete the workspace
Settings shows each person only what their role can change. A member's Settings menu has Notifications, Profile, Security and a read-only Team page that names the workspace's admins. If a member opens an admin page from an old link, it explains in a sentence what is set and who to ask, with no form.
Adding and removing repositories is an admin capability because repositories are what your plan counts: connecting one spends allowance, and removing one throws away the work Watari did to get that code ready, which takes real time to redo. Reading a repository you already have connected again is not, because it changes neither.
Suggesting code owners is an admin capability too. Using a suggestion opens a pull request in your
repository that adds a CODEOWNERS file, so it reaches further than the branch settings. Members can
still see who owns each folder on Codebase → Who owns this code.
Asking Watari to search the code again for an issue is an admin capability because a new search can find a Strong match where there was none, and an issue with a Strong match can count as a Mapped Issue on your plan. Starting a draft fix and trying it again with more detail stay open to every member: neither searches the code again, so neither is ever billed.
Every workspace has exactly one Owner: the person who created it. The Owner role cannot be transferred or removed. Admins and Members can be removed by the Owner or any Admin.
Connected tools belong to the workspace, not to the person who connected them, so removing a member does not disconnect anything. What can break it is the other side: if that person's Zendesk, Jira or Intercom account is deactivated when they leave, the access Watari was granted through them can be revoked at the provider. Watari marks the tool as stopped working and notifies your owners and admins when that happens, and any admin can reconnect it. If someone is leaving and they are the person who connected a tool, reconnecting under another account first avoids the gap.
Password
Go to Settings → Security and enter your current password and a new one. Changing it signs you out on any other device, and this one stays signed in.
If you sign in with Google, you have no Watari password to change, and the page says so. If you have forgotten your password, sign out and use Forgot password on the sign-in page.
Two-factor authentication (MFA)
Each team member manages their own MFA enrollment. Admins should enroll, it's strongly recommended.
Go to Settings → Security.
Click Add authenticator app.
Scan the QR code with an authenticator app: 1Password, Google Authenticator, Authy, or any TOTP-compatible app.
Enter the 6-digit code to confirm enrollment.
After enrollment, Watari prompts for the 6-digit code on every sign-in. You can have multiple authenticators enrolled, useful if you use more than one device.
Lost access to your authenticator? Email support@watari.ai from the address registered on your account. We verify your identity and remove the factor manually. Self-service MFA reset is not available, recovery requires a support ticket.
Profile
Update your display name, email address, and avatar at Settings → Profile. Your display name appears on the team members list and on any activity attributable to your account (mismapped reports, customer update approvals).
Switching workspaces
If your Watari account belongs to more than one workspace (for example, a client workspace and your own) use the workspace selector in the top-left of the dashboard to switch. Each workspace has completely separate data, connected tools, and billing.
Next: How Watari works: when Watari drafts a fix on its own, when your customer hears, and the settings your engineers may want to adjust.