Apps

What are Go Apps?

An app can present information and let users take actions without requiring them to navigate each underlying resource separately. This could be a review interface, a dashboard, or a public submission form. People open a Go App to review work, enter data, or run a task. Go keeps the workflows, Playbooks, files, and models behind that screen, and only exposes what the App interface.

Building an app

To build an app, navigate to the "Apps" section of your workspace and start a new chat.
Decribe:

• What your app should do
• The Go features it should connect to (specific workflows, playbooks, data stores)
• What it should look like

Go will do the work to create a preview and display a card with the app's source files. Contact the V7 team to publish an app preview.

Publishing, availability, and access

New published app are only visible to workspace admins, giving them time to test and iterate before opening access more broadly.

When the app is ready for wider use, contact the V7 team to make it open to the whole workspace. An app installation can be restricted again if needed.

Apps check the signed-in user’s permissions when accessing workflows, including for read-only views. Access to an app does not grant access to its underlying workflows.

For example, if an app uses two workflows and a user only has access to one:

• They can view information from the workflow they have permission to read.
• They cannot retrieve information from the other workflow, even for a read-only chart or table.
• They can only make changes or trigger actions where both their permissions and the app’s granted permissions allow it.

Supported functionality

An app can work with multiple resources, subject to its granted permissions and the signed-in user’s access.