Skip to content

Give people access to apps only

An App User is a member of your organization who opens only apps: floor staff who use a shift-planning app, or a site manager who uses one report. They sign in with Ronja like everyone else and land on Your apps, which shows the apps they can open and nothing more. They don’t chat with Ronja, and they can’t open features, tables, notes or files.

An App User opens two kinds of apps:

App User is one of the five roles. Being a member, an App User can hold people properties, and an app can list them for the people who hold a value, such as everyone at Site: Malmö.

To invite someone as an App User:

  1. In the admin area, go to Users & Access and click Invite users.
  2. Enter their Email addresses.
  3. Under Role, choose App User. The dialog describes it: “Opens only apps: the ones their access groups reach and the ones listed for them. No chat, files or data.”
  4. Click Send invite.

To make an existing member an App User, pick App User in their row’s role control, on their own page, or with Change role for several people at once. Ronja asks first, for example Make Erik Svensson an App User?: “Erik Svensson will open only apps: the ones their access groups reach and the ones an Admin lists for them. They lose chat, files and data.” They stay in their access groups, which now open them only those groups’ apps. Automations they own keep running, except an older automation that runs Ronja’s agent as them, which stops (see An automation didn’t run); the dialog names the ones they own. Click Make App User to confirm.

A new App User opens the apps their access groups reach straight away. In most organizations the Default access group includes everybody and shares every Organization feature, so a new App User opens every app in those features. To keep them to a few apps, see Keep App Users to chosen apps.

A registered login domain can also let people join as App Users: choose App User under New members join as.

An App User in an access group opens the apps that group reaches, exactly as its other members do:

  • the apps in the features the group shares with Full access, including through All features;
  • for a feature the group shares with Selected resources, only the apps selected;
  • never an app in a private feature or in the trash.

This includes groups with Everyone on, such as the Default one: an App User is in them like everybody else in the Space. A group works inside its Space, so it reaches only App Users in that Space. An access group gives an App User its apps and nothing else: not the features, tables, notes, files or chats it shares.

Add an App User to an access group the way you add anyone: on the group’s Members tab, or in its column on Users & Access, alone or with Add to group for several people. Whoever may add people to a group may add an App User, the group’s own admins included. They are marked App User there, and hovering their cell reads “App User: opens this group’s apps only”.

On an app’s Access tab, under App Users, Through access groups lists each group through which an App User opens the app, linked to its Members tab, with the App Users it lets in. A group with Everyone on reads “Every App User in” its Space. The list is read-only: change who is in a group on the group’s page.

Because an App User opens whatever their access groups reach, keep them to chosen apps through those groups:

  • Narrow what an Everyone group shares. If the Default access group shares all features, every App User opens every app in them. Turn its All features off and attach only the features everybody should reach. See The features an access group reaches.
  • Use a group of their own. Put App Users in an access group that shares only the features they need, or a feature with Selected resources and only the apps they need selected, and keep them out of groups that share more.
  • List them per app. An app’s App Users section lets an App User in on that app alone, whatever their groups reach.

The app needs an address (publish it to give it one) and must be in a feature shared with the organization.

  1. Open the app’s Details and go to the Access tab.
  2. In the App Users section, click Add App Users.
  3. Under Find App Users or values, search by name, by email, or for a people-property value such as Site: Malmö, and tick who to add. An App User a value on the app already lets in is listed last, marked “Already allowed by Site: Malmö”; tick them too to keep them on the app if they lose the value.
  4. Click Add (or Add 3 for three).

A value lets in every App User who holds it, checked each time they open the app. Give Erik the value Site: Malmö and he can open the app; move him to Site: Göteborg and he can’t the next time he opens it. An app he already has open stops loading data within 30 seconds. The value dialogs on People properties say which apps a change opens or closes for App Users, and a value an app lists can’t be deleted until it is removed from the app.

The section lists each App User by name and email, and each value with how many App Users hold it today, such as “Site: Malmö · 8 App Users today”. Only App Users can be listed: other members open an app through its feature. Below the list, Through access groups shows the groups that let App Users in as well (above). An app can list up to 200 App Users and values; past that, list a value instead of naming people.

Adding App Users to an app is browser-only: it refuses an API token, the CLI and automations. Removing them stays scriptable. See Actions the API can’t take.

  • From one person or value: click Remove on the row in the App Users section, then Remove in Remove from this app. They lose the app within about a minute, unless another row on the app or one of their access groups still lets them in; the dialog says so, and so does the line after it, for example “Still allowed by Site: Malmö” or “Still allowed by Warehouse”.
  • Through access groups: remove them from the group, or take the feature or the app off the group. They lose the group’s apps the next time they open one, and an app they have open stops loading data within 30 seconds.
  • By changing their role: an App User given another role leaves every app’s App User list, and the dialog says how many, for example “This removes them from 3 apps’ App User lists.” Given a member role, they stay in their access groups, which then give them everything those groups share, as for any member. The dialog always says so: “Their access groups then give them everything those groups share, not only apps.”
  • By removing them from the organization: they lose every app at once.

Your apps lists the apps they can open, each opening on its own page. On that page, ← Your apps in the bottom-left corner takes them back to the list. A card names the app’s organization only when the apps come from more than one. With none, it says “You can’t open any apps here yet.” and asks them to contact an Admin. Below the list are their name, “App User in” your organization, Edit name, Switch organization (for someone in more than one organization) and Sign out. Every other page in your organization answers “Not open to App Users”.

A link to one of their apps inside Ronja takes them straight to the app. A link to any other app shows Your apps with “The app in that link isn’t one of yours.” A link into a chat with Ronja, such as Build this in Ronja in Slack or Teams, shows Your apps with “Chat with Ronja isn’t open to App Users. Ask an Admin if you need it.”

App User
Open the apps their access groups reach, and the apps listed for them Yes
Use an app’s own chat panel Yes
Appear in an app’s list of people, with their people properties, and read that list Yes
Open and upload files inside an app Only in the folders listed on the app (below)
Chat with Ronja, in Ronja or in Slack and Teams No: “You can open apps in” your organization, “but not chat with Ronja.”
Open features, tables, notes or files, or search No
Use API tokens, the CLI or an AI assistant connected to Ronja No
Get notifications No
Be added to an access group Yes: the group opens them its apps only
Be picked to share a chat, a project or a folder with No

Files. Inside an app, an App User opens and uploads files only in the folders listed under Folders guests and App Users can use, in the app’s Guests section; see Folders for guests, whose rules apply to App Users too, the upload limit included. A file the app links to outside those folders shows as missing for them. On the Files page, a file an App User uploaded through an app shows the app’s name under Owner, marked App User; hover it to read “Uploaded by an App User through” and the app’s name.

Notifications. A notification meant only for an App User goes to your organization’s Admins instead and says why: “Sent to the organization’s Admins because Erik Svensson is an App User and gets no notifications.” Automations an App User owns keep running, except an older automation that runs Ronja’s agent as them, which stops (see An automation didn’t run). Failure notices for their automations reach the Admins the same way.

Usage. What an App User does in an app is charged to the app, as for any member, and their visits count on the Activity page’s Apps tab.

A guest is someone outside your organization; an App User is a member. Both land on Your apps, both are shown on each app’s Access tab, and both use only the folders listed on the app. The differences:

App User Guest
Who they are A member of your organization Someone outside it, never a member
Opens an app through Their access groups, or a listing by name or people-property value A listing by email address or domain
Which apps Any app with an address in a shared feature Only apps opened to guests, with Server-side data only on
Access groups Yes, apps only No
An app’s people list and chat panel Yes No
People properties Yes No

A guest who needs more, such as people properties, becomes a member: invite them with the email address they sign in with and choose App User under Role. See Make a guest a member.