TattvaDocs
Trust & administration

Workspaces & members

How a workspace is organised, the five roles, who does the data analyst's work, and how to invite people.

A workspace is your company's space in Tattva. It holds members and projects. Each member has one workspace role, and that role applies in every project unless a project gives them a different one.

The Settings hub

Where to find it

Open Settings and choose the Workspace tile, or go to /settings/workspace.

The five roles

RoleWhat it is for
OwnerRuns the workspace. Can do everything, including deleting the workspace and reading the audit log. The owner's role can't be changed from this screen.
AdminManages people and projects: invites members, changes roles, grants PII clearance, creates projects, deletes boards, reviews promotion requests.
MemberThe day-to-day role: asks questions, uploads sources, creates trackers and boards.
ViewerReads projects and the ontology. A viewer can't ask questions, upload sources or create anything.
Ontology AdminThe data analyst's role. Acts like a Member everywhere, plus authority over the shared ontology: writes to the Workspace Library, reviews promotion requests, edits value groupings and family policies, approves value mappings from conflicts.

Ontology Admin sits beside the other roles rather than above or below them. Give it to the people who own your company's metric definitions. Admins and Owners can also do everything an Ontology Admin can.

PII clearance is set separately from the role. A Viewer can hold full clearance and an Admin can hold none. See Sensitive data.

Who does the data analyst's work

Tattva's answers are only as good as the definitions behind them. Someone in your team has to own that work. Usually that's a data analyst with the Ontology Admin or Admin role. The full guide is in For data analysts.

What the data analyst does:

  • Connects and describes data. Adds BigQuery tables and uploads, checks column meanings on each source's Schema tab, and marks sensitive columns. See Connect and describe data.
  • Writes metric documents. Uploads a .md or .txt file that defines your metrics with SQL, then runs a build from the Ontology page. See Write a metric document.
  • Reviews what the build proposes, and answer feedback. Works through Ontology › Maintain › Review: reads each candidate's checks, then chooses Accept, Defer or Reject. Works through Ontology › Maintain › Feedback: each Not satisfied comment members leave under an answer, marking it In review, adding a team note, and turning it into a convention or correction where needed. See Review what Tattva proposes and Answer feedback.
  • Shapes how questions are answered. Sets the variant policy on metric families and groups column values so names people use match the data. See Families and Inputs and groupings.
  • Keeps the ontology healthy. Reads Health and Conflicts after each build, resolves conflicts, and approves or rejects requests in the Promotion Inbox. See Maintain the ontology.

Agree who reviews

In any project other than the Workspace Library, deciding in Maintain › Review is not limited by role: every member of the project can accept, defer or reject candidates and review corrections. The same goes for resolving most conflicts. Accepting a metric definition changes the numbers every answer and tracker uses. Agree in your team who reviews, and leave the queue to those people.

The actions below do check the role:

ActionWho can do it
Approve or reject a request in the Promotion InboxOntology Admin, Admin, Owner
Edit value groupings (Group as)Ontology Admin, Admin, Owner
Approve a value mapping from a conflictOntology Admin, Admin, Owner
Change a family's variant policy or a metric's settlementOntology Admin, Admin, Owner
Decide in Maintain › Review on the Workspace Library project (accept, reject, defer, back to pending, review or delete a correction)Ontology Admin, Admin, Owner
Start an ontology build (Regenerate, Build Ontology →, Rebuild), in any projectOntology Admin, Admin, Owner
Write to the Workspace LibraryOntology Admin, Admin, Owner

The Workspace screen

Workspace settings: General and Members

  • Header: the workspace name and a count of members and projects.
  • General: Name (editable) and Slug (read-only). Save is enabled once you change the name.
  • Members: an invite row, then one row per member with their name and email, the date they joined, their role, their PII clearance chip, and a remove icon. Someone invited who hasn't signed in yet shows Invited, not signed in yet and the date they were invited.
  • Danger zone: shown to owners only. Delete workspace… opens a dialog.

Inviting a member

  1. Type the person's email in the invite row.
  2. Pick a role: Admin, Member, Viewer or Ontology Admin. The default is Member.
  3. Click Invite.

The member appears in the list right away. Tattva doesn't send an invitation email, so tell the person yourself. When they first sign in with Google using that email address, the access is already there.

Only Admins and Owners can invite. If anyone else tries, the server refuses and the member simply doesn't appear; the screen shows no error.

Changing a role

Use the role menu on the member's row. The choices are admin, member, viewer and ontology_admin. Owners show a fixed owner chip instead of a menu. Only Admins and Owners can change roles, and each change is written to the audit log.

Granting PII clearance

Click a member's PII chip (none, aggregated, unsafe agg or full) to open Manage PII access. Pick a tier, write a justification, optionally set an expiry, and click Save grant. Only Admins and Owners can do this. See Sensitive data for what each tier sees.

Removing a member

Click the remove icon on a member's row and confirm Remove member?. Their access to the workspace ends at once, and the removal is written to the audit log. Owners have no remove icon. Only Admins and Owners can remove members; if anyone else tries, the server refuses and the screen says so.

Removing someone who was invited but never signed in withdraws the invitation.

Slack channels

A Slack channel can ask Tattva through Manas when someone @mentions Manas in it. For that, the channel has to be connected to a project. Connected channels are listed under Settings › Workspace › Slack channels, separately from people, for the current project.

To connect a channel, enter its channel id (for example C0123ABCD; in Slack, open the channel's details to find it) and its name without the # (for example sales-leads), then click Add Slack channel. Only Owners and Admins can add or remove channels; everyone else sees the list.

A connected channel has fixed limits, whatever anyone does:

  • It can only ask questions, read the project and its definitions, and leave feedback on an answer (which waits in Ontology › Maintain › Feedback for the team; see Work answer feedback). It can't upload, review, edit the ontology or create anything.
  • It never sees personal data. Answers in the channel are always masked, whatever the people in the channel are cleared for.
  • Nothing it asks is saved to project memory.
  • Its conversations are read-only for everyone else in Tattva.

Click Remove on a channel's row to disconnect it. Access is revoked at once; the next @mention in that channel is refused.

A channel is represented by an address of the form slack-c0123abcd@kapiva.in. Addresses of the form slack-…@kapiva.in are reserved for channels: they can't be invited as people and can't sign in.

A channel's default project

A channel can be connected to several projects. Each channel's row lists all of them, and one is marked Default: that is where an @mention goes when it doesn't name a project. The first project a channel is added to becomes its default; adding it to more projects doesn't change that.

To change it, click Make default next to another of the channel's projects. Owners and Admins of a project the channel is in can do this; the change is written to the audit log. It only changes where questions go, not what the channel can see.

Removing a channel from its default project clears the default. If the channel is still in several projects, the row says "No default: Manas asks which project" until someone clicks Make default; until then Manas asks which project on each new question.

See Use Tattva from Manas for what people in the channel see.

Deleting the workspace

Owners see Delete workspace… in the Danger zone. The dialog asks you to type the workspace slug. Deleting removes every project, decision, tracker, ontology and uploaded document in the workspace, and it can't be undone.

Tips

  • Keep at least two Owners, so the workspace never depends on one person.
  • Default new people to Member. Use Viewer only for people who read but never ask.
  • Give Ontology Admin to the people who own metric definitions, and nobody else.
Workspaces & members — Tattva Docs