People properties

Who can do this

Admin. Changing people properties is browser-only: the API and the CLI can read them but can’t change them (see Actions the API can’t take). Every member can read them.

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, and apps can tailor themselves to the person looking at them.

Create a property

1. Click Admin in the sidebar, then People properties (under People & Access, next to Users & Access).
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.

Add values

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. 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.
• Delete property, at the bottom of the page, does the same for a whole property and all its values.
• To rename a property or change its description, edit Name or Description under Settings, below the values, and click Save changes.

Give people a value

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.

To take a value away from someone, click the × beside their name. A person can have up to 20 values on one Several values property.

From a person’s page

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; 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 Delete user and Remove from organization both warn. If they come back, they start with none.

Import from a file

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.

What Ronja does with properties

• 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?”), so your organization policy can say things like “when the person is a Technician, …”.
• In an app, the app 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). It uses them to tailor what it shows, never to decide who may see what.

Keep sensitive facts out

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.