Skip to content

People properties

A people property is a fact you record about each person in your organization, such as their Region, Job role or Site. A property has values, the choices people can have: Region might have North and South. Each person has one value, several on some properties, or none.

Ronja then knows who she is talking to beyond a name and an email, apps can tailor themselves to the person looking at them, and a value can let App Users into the apps that list it.

  1. Click Admin in the sidebar, then People properties (under People & Access, below Guests).
  2. Click New property.
  3. Enter a Name (for example, Region) and, if you like, a Description.
  4. Under Each person has, choose One value or Several values. A job role suits One value; regions or sites a person covers suit Several values. You can’t change this later; create a new property instead.
  5. Click Create property. The property’s page opens.

An organization can have up to 20 properties.

A property’s page lists its Values first, then Settings, the people with No value, and Delete property at the bottom.

Click Add value beside the Values heading (on a property with no values yet, it’s under No values yet), enter a Name such as North, and click Add value. A property can have up to 500 values, listed alphabetically.

Each property and value also has a Key, such as region and north: a property’s key is shown under Settings, and each value’s key is shown beside the value, with how many people have it. Apps use the key. Ronja sets it from the name, and it never changes, even when you rename.

  • Rename a value from its row. The key stays the same, so apps keep working.
  • Delete value removes it from everyone who has it, and the dialog says how many people that is. A value an app lists for App Users can’t be deleted: Ronja refuses and names the apps (“… is used by the App User rules of …. Remove those rules first.”). Remove it from each app’s App Users section first. Apps using its key stop matching it. To undo, add a value with the same name: it comes back with the same key and nobody in it. If the value has a policy, the dialog also says the policy stays with the Organization policy and applies to nobody until you remove it or add the value again.
  • Delete property, at the bottom of the page, does the same for a whole property and all its values, and is refused the same way while an app lists any of its values.
  • To rename a property or change its description, edit Name or Description under Settings, below the values, and click Save changes.

Each value can have its own short policy telling Ronja how to work with the people who have it, such as “Lead with the answer and the number; no code unless asked” for CEOs. A value without one shows “No policy. Tell Ronja how to work with people who have Technician.”

  1. Click Add policy on that line, or Edit policy on a value’s Policy.
  2. In Policy for Technician, write a few lines (up to 500 characters, no headings). Insert reference points at a note, table or feature.
  3. Click Save policy.

The dialog says who the policy applies to, and warns when some of them can’t open something it references, so Ronja can’t read it in their chats. Empty the text and save to remove the policy. A saved policy shows under the value with Part of the Organization policy · version 7. See Policies for people properties for where it applies and who wins when rules disagree.

  1. On the property’s page, click Add people beside a value.
  2. Search under Find people, tick the people who have this value, and click the button that counts them, such as Add 3 people.
  3. On a One value property, anyone who has a different value moves out of it. The dialog lists who moves and saves only when you click Move them; Change who to add goes back to the list.

When a value is listed on apps for App Users, the property’s page says so under the value, for example “App Users with Malmö can open Shift planning.”, and Add people says which apps the change opens for the App Users you are adding and, on a One value property, which apps the value they leave closes for them, “unless another rule on the app lists them”. The change takes effect the next time they open the app.

To take a value away from someone, click the × beside their name. If they are an App User and the value is listed on apps, you’re asked first, with the apps it closes for them: click Remove to confirm. A person can have up to 20 values on one Several values property.

Every person’s page under Users & Access has a Properties section. Open a person’s Settings from the matrix (see Manage users and roles), then:

  • One value property: pick a value, or No value, and click Save. If that moves the person out of a value they have, you’re asked first: click Move them to confirm.
  • Several values property: pick from Add value… and click Add, or click the × on a value to remove it.
  • Removing a value saves right away, unless the person is an App User and the value is listed on apps: then you’re asked first, with the apps it closes for them, and click Remove to confirm. Other changes need Save or Add. A choice you haven’t saved yet shows Unsaved changes beside its button, and a property shows Saved for a moment once its change is saved.

When someone leaves the organization, their properties go with them, as Remove from organization warns. If they come back, they start with none.

If your directory is in Microsoft Entra ID or Google Workspace, you can set job titles, departments and offices from its user export instead of by hand. See Import people properties from a file.

  • In a chat, Ronja knows the properties of the person she is talking to and can list who has which value (“Who are the technicians in North?”). She follows the policy for each value the person has, in the app and in Slack or Microsoft Teams, and never in an automation or a Saved Agent run. Each person sees those policies on Your policy, with why each applies.
  • In an app, the app’s page can read the properties of the person looking at it, for example to open on their own region, and list who has a value (see Build an app). The page uses them only to tailor what it shows, because it could change them. To decide what each person may see, the app’s server functions read the properties of the person calling them, which nothing in the app can change: an app built that way, with Server-side data only on, shows each person only the rows their values allow, such as their own restaurant’s orders. See Show each person only their own data.
  • On an app’s Access tab, an Admin can list a value under App Users, so every App User who holds it can open the app, checked each time they open it. That is the one place Ronja itself decides access by a property, and only for App Users. See Give people access to apps only.

Every member can see everyone’s properties, through Ronja and through apps, so record only facts you would show the whole organization. Anything sensitive, such as a salary band or a health status, belongs in a table, where you control who has access. The same goes for a value’s policy: every member, and every API token that can read the organization policy, can read every value’s policy, so nothing sensitive belongs in one.