Apps
Apps are working tools AI builds inside a Space. Use them for product dashboards, CRMs, trackers, intake forms, review queues, project boards, and internal workflows.
An app can use persistent data and stay securely available to your team. It lives in the Space Library with the thread that created it, so everyone can understand where it came from and keep improving it.
Build an app
Section titled “Build an app”Describe the job, data, views, actions, and access the app needs. AI can build a first version and show it in the thread.
From there, your team can prompt together, comment, select part of the app, and ask AI to change it. The working version updates as you iterate.
Keep the request specific. Name the fields, filters, workflows, and decisions the app should help with.
Review and publish updates
Section titled “Review and publish updates”Updates to an existing app are prepared as a shared draft. The live app stays available while your team reviews the changes.
The Live app / Draft preview menu appears for app editors and owners while a shared draft is available. To update the app’s views or behavior from the Library, choose Open in Thread and ask AI to prepare the changes for review. Connection choices can also create a draft through App connections, as described below. Interacting and Commenting control how you use the app; they do not create a draft.
- Open the app from its thread or the Space Library and ask AI for the update.
- Use the app view menu to switch between Live app and Draft preview. Wait for draft preparation to finish, then try the updated views and actions.
- Choose Publish update when the draft is ready. If it adds integration access, choose Review & publish and review the accounts and actions before allowing access.
- After publishing finishes, check the live app to confirm the update.
If the draft says Draft needs attention or Draft unavailable, ask AI to resolve the problem and prepare it again before publishing.
To abandon an update, open the app view menu, choose Discard changes, and confirm. This permanently deletes the shared draft, its preview, and data created while testing it. The live app stays unchanged.
Use connected services
Section titled “Use connected services”AI can use the Space’s connections to build and update an app with business data. Published apps can also run approved integration actions, such as reading records or updating a connected service. The app receives the results of those actions, not the connection’s sign-in details.
When publishing adds integration access, Review access before publishing lists the services and actions. Check each action’s label: Read-only, Can make changes, or Can delete data. Confirm that the app needs those actions before choosing Allow access & publish.
Know whose account the app uses
Section titled “Know whose account the app uses”Each connection used by an app has its own account choice. App connections shows the supported Run as options:
- Shared team connection: Everyone runs the approved actions through the shared team account.
- Publisher’s personal connection: Everyone runs the approved actions through the publisher’s account. Where personal-account sharing is enabled, only that account’s owner can consent; another Space admin cannot approve on their behalf. Review the app’s audience before consenting.
- Each viewer’s personal connection: Each signed-in person runs the actions through their own eligible connection and that account’s permissions. Viewers use their own Type accounts; they do not need separate copies of the app.
An app can use different choices for different connections. Services that need no account show No authentication required. Account choices are saved in the draft and take effect after publishing.
Change an app’s connection choice
Section titled “Change an app’s connection choice”App editors and owners can open App connections from the app’s menu, including when no draft exists. Opening it does not change the app. To choose Each viewer’s personal connection, you must already have a valid personal account for that connection. This option is available only for interactive actions. If the connection also runs automatic background reads, ask AI to revise the app before switching it; background actions cannot choose a viewer’s account.
- Open the app’s menu and choose App connections.
- Find the connection, choose its Run as option, then choose Save.
- Wait for the draft to finish preparing, then test it.
- Choose Review & publish or Publish update and complete any access review.
Save creates a connection-settings draft or updates your existing draft, preserving its other changes. The live app stays unchanged until you publish. If another person authored the draft, or the app or source changed, resolve that conflict before saving. Only connections already used by the app appear here; if there are none, the dialog shows an empty state. Ask AI to add a service if it is missing.
If AI cannot prepare a connection requested for a live app, it should explain the blocker and ask you before replacing live data with a static snapshot. An agreed snapshot should show its source and capture date and say that it does not refresh automatically.
You can also prepare a connection-only update with the Type CLI, review its hosted draft, and publish separately after approval. See Type CLI: Change an app’s connection account choice for the commands and settings to preserve.
Choose your personal connection
Section titled “Choose your personal connection”When an app uses each viewer’s account, Type automatically uses a single eligible personal connection when you first run an action. If you have several, Choose your connection lets you select one and choose Use connection. Type remembers your choice for that app.
For NetSuite, an existing personal connection in the same Type workspace can qualify even if it is separate from the app author’s connection. It must be available to the app’s Space and support the app’s approved actions. You do not need to reconnect an eligible account just to use the app.
If no connection is available, use Open Connections to connect your account or review its access to the Space. Reconnect expired or revoked credentials, or ask someone who manages connections to check your permissions. Then retry the action. If a saved choice becomes unavailable, Type asks you to choose again instead of silently switching accounts.
Review requests while using an app
Section titled “Review requests while using an app”Interactive integration actions require a signed-in workspace member with access to the app. Type also checks the approved connection when an action runs; sharing a public link does not grant anonymous access to connected services. If an action needs an initial Space permission grant, a Space owner or admin must approve it.
Type asks for confirmation each time an action can delete data, and each time an action makes changes through a person’s connected account. Review the actual request before confirming. Ordinary actions covered by an existing approval can run without repeating that approval.
Where automatic read actions are available, the publishing review marks them Runs automatically. Open Review saved request to inspect the request and its daily limit. Personal-account automatic reads require separate consent. These approvals cover the saved read requests; they do not authorize arbitrary background changes.
Keep data current
Section titled “Keep data current”Use Automations when the app should refresh or reconcile data on a schedule.
For example, an automation can:
- Refresh a dashboard every morning.
- Add records found during a recurring sweep.
- Compare app data with a connected source.
Use an automation for broader recurring workflows; use an approved automatic app read when the app only needs to refresh a specific saved request.
Find apps in the Library
Section titled “Find apps in the Library”Apps become part of the Space Library. Open an app from the Library to use it, review its history, or jump back to the threads that changed it.
The same Space can hold the app, the documents that explain it, the skills used to maintain it, and the conversations where your team makes decisions.
Develop an app locally
Section titled “Develop an app locally”Claude, Codex, and other local development tools can check out a Type App with the Type CLI, run its frontend locally, and use a Type-managed Convex development backend. The CLI synchronizes the complete authored source tree without requiring a Git repository and stops instead of merging divergent edits automatically.
Local development updates shared editable source but does not automatically create a hosted draft. Push an update when it is ready for hosted review, then publish it separately. The first push for a new app is the exception: it creates the initial live release and requires explicit confirmation.
See Type CLI: Develop Type Apps locally for setup, synchronization, conflict recovery, publishing, and access safety.
Share an app
Section titled “Share an app”An app can be shared with specific people, private Spaces, the workspace, or through a public link when workspace policy allows it.
Anyone with access can use the app and its data. Review both before sharing outside your team.