Reader groups let some of your docs be for some readers only, such as customers on your Enterprise plan or your beta testers. A group is made of conditions on your users' properties: anyone whose properties match is in it, now and as their properties change. Reader groups are on the Business plan. Owners and admins manage them in Settings → Groups.

Where properties come from

Properties are what your app tells Tuti about each of its users, like plan, role, seats or company. Your app sends them in two ways:

  • In the sign-in token, when it signs people in with single sign-on. The token's groups becomes the groups property.

  • Through the API's users.sync, for users who haven't signed in yet.

Each sign-in or sync changes only the properties it names, and the rest stay. Users shows each user's properties. See See your users and the companies they're at and Name and format your users' properties.

Add a group

  1. Open Settings → Groups and choose New group.

  2. Enter a Name, like "Enterprise", and a Description (optional) for your team.

  3. Under Conditions, fill in the first one: the property's name, like plan, an operator, and the value, like enterprise. Property names your users already have are suggested as you type.

  4. To narrow it down, choose Add condition. All conditions must match. A group has 1 to 10 conditions.

  5. Choose Add group.

While you write, the right side of the dialog lists the users who match now: how many, and the first 50 by name.

The New group dialog with two conditions, plan is enterprise and role is admin, and the three users who match

Operators

Operator

Matches when the property…

Value

is / is not

is (or isn't) the value

One value

is any of / is none of

is one (or none) of the values

Values separated by commas, like pro, enterprise

contains / excludes

has (or doesn't have) the value in its text, like company contains Acme

One value

is set / is not set

has a value at all (or doesn't)

None

How values compare

  • Values compare as text, exactly. Capital letters and spaces count: Pro isn't pro. The property's name must match exactly too.

  • Numbers and true or false compare as their text: a seats of 12 is 12, a beta of true is true.

  • A list property, like groups, matches is, is any of and contains when one of its items does. It matches is not, is none of and excludes when none does.

  • A user without the property, or with an empty list, matches only is not, is none of, excludes and is not set.

For people your app puts in its "beta" group, use the condition groups is beta.

Who can be in a group

Only your app's users can be in a group:

  • People your app signs in with single sign-on.

  • People signed in to your portal another way, like with an emailed link, whose verified email address is one of your users' email. They get that user's groups.

Signed-out visitors and everyone else are in no group, even one whose only condition is is not. Your team reads everything anyway.

See and change groups

The list in Settings → Groups shows each group's conditions, how many users are in it now with a few of their names, and its description.

The Groups list with Beta testers, Enterprise and Paying customers

  • Edit opens the same dialog. Changing the conditions changes who's in the group straight away.

  • Delete removes a group for good. A group that a docs tab, collection or article is for can't be deleted: Tuti says "Used by …; remove it from them first".

Use a group

In your docs, pick the group under Who can read on a tab, a collection or an article. See Choose who can read each page of your docs.

If your plan changes

On a plan without reader groups, Tuti keeps your groups, but docs for groups are your team's only until the plan is back. Settings → Groups says so at the top, with See Billing.