Roles and permissions

Everyone with access to an app has one of four roles. You choose it when you share, and can change it from Who has access.

Role	Can
Can view	Open the app and see its data. Changes nothing.
Can use	Everything above, plus add and change data and files, use the app’s AI, join multiplayer, and send the app’s notifications. The default.
Can edit	Everything above, plus open the app in Studio and publish new versions.
Can manage	Everything above, plus share with people, change their roles, answer access requests, and link integrations to the app.

The owner — whoever created the app — can do all of that, and is the only one who can:

• change General access and visibility;
• add the app to groups, remove it, or change a group’s role;
• turn remixing on or off;
• change the app’s name, description, category and cover;
• delete the app.

How roles combine

Someone can reach an app several ways at once — invited directly, through two groups, and by the link. They get the strongest role among them.

• Groups can be given Can view, Can use or Can edit, never Can manage.
• The link gives at most Can use, and only to signed-in people; anonymous visitors are always view-only.

Groups don’t own apps

Sharing an app into a group as Can use lets members use it. It gives the group’s owner and admins no say over the app’s data, versions or settings — they can only remove it from their group. The app and its data stay with its owner. See Groups.

Inside the app

Apps see each person’s role and enforce it: a Can view visitor sees a read-only app. App developers: see Identity and permissions.