Share an app with your teammates

An app you build in Onplana belongs to you and starts out private. Nobody else in your workspace can open it, run it, or read what it is made of until you share it, and you share it one app at a time rather than switching on a workspace-wide setting.

This is not the same as who can use your published app

This article is about giving colleagues in your workspace access to the app itself. If you have published an app to a live URL and want to control which visitors can open it, that is a separate setting, covered in Control who can use your published app. You can use both: the two do not overlap.

Private means invisible, not just locked

A teammate you have not shared with does not see a locked app or a “you do not have access” message. They do not see the app at all, and opening its address tells them nothing exists there.

That is deliberate. An app’s name can give away a project, a client, or a launch, so an error that admits it exists would leak something even to somebody who cannot open it.

The two levels

When you share an app you pick one of two levels for each person or team.

	Read-only	Full control
Run the app	Yes	Yes
Ask questions about it	Yes, read-only	Yes
See its details	Yes	Yes
Read the source	No	Yes
Export it	No	Yes
Build on it and change it	No	Yes
Share it with others	No	No

Read-only suits the people you want to use what you built: they can open the app and work with it, and ask about it, without seeing how it is put together.

Full control suits a collaborator who is going to work on the app with you. It adds everything source-bearing, so treat it as handing over the code.

Sharing itself stays with you. A colleague you gave full control to cannot pass access on to somebody else.

Publishing is a separate permission

This is the part that surprises people, so it is worth stating plainly.

Giving somebody full control does not let them publish your app. Publishing to a live URL needs a workspace-level publish permission as well, which an Admin grants separately. Someone can hold full control over your app, change it freely, and still have no ability to put it on the internet.

The reverse also holds: holding the publish permission does not give anybody access to an app you have not shared with them.

Who already has access

Some people can reach the app without you sharing it:

• You, as the creator, always have the highest level, including sharing.
• Owners and Admins of the workspace have the same, so they can help when somebody leaves or an app needs handing over.
• Anyone whose role grants them visibility across all projects gets read-only oversight, not the ability to change or export anything.

Who cannot be granted

Guests cannot be given access to an app, at any level. Guests are usually outside collaborators, and an app can carry source, keys, and customer data.

That holds even if the guest is a member of a team you share with. Team membership does not carry a role with it, so Onplana checks each person individually and skips the guests rather than letting a team grant become a side door.

Deactivated members cannot be granted either. Teams themselves are fine to share with, and are the tidier option when the same group needs access to several apps.

Steps

1. Open the app in Build.
2. Choose Share.
3. Pick the person or team.
4. Choose read-only or full control.
5. Save. Access applies straight away.

To take access away, return to the same panel and remove the entry. Removal is also immediate.

Onplana Maker is single-player for now

Maker workspaces have one owner, so sharing an app with a teammate is not available there yet, and the Share panel says so. Publishing the app to a live URL is how you put a Maker app in front of other people today. Sharing works in the full Onplana app.

Common questions

If I share read-only, can they see my code? No. Reading the source, exporting the app, and downloading its files all need full control.

Can somebody I shared with delete my app? No. Deleting is not part of either level.

Does sharing an app share the data it collects? The app’s own data follows the app: somebody who can run it sees what it shows. If your app collects form submissions, treat read-only as access to those submissions too.

Can I share with somebody outside my workspace? Not through this. Sharing is for workspace members and teams. To reach people outside, publish the app and use the visitor access controls in Control who can use your published app.