Publish

Documentation Index

Fetch the complete documentation index at: https://help.notis.ai/llms.txt

Use this file to discover all available pages before exploring further.

Publishing turns a private app into something other people can install. There are two channels: Team (only your team members) and Public (anyone with a Notis account, after review).

​

Where listing metadata comes from

Notis pulls listing metadata directly from the deployed app — not from the portal UI. Everything users see in the store comes from your repo: Update those fields, run notis apps deploy, and your next publish picks them up. Listing copy lives with your code, where you can review it in PRs.

​

Set visibility

Before publishing, open App Details (/apps/[appId]) in the Notis portal and pick a Visibility:

• Personal — only you can install it. The Publish button is disabled.
• Team — your team members can install it.
• Public — anyone with a Notis account can install it, after review.

You can change visibility at any time.

​

Publish to your team

1. Make sure visibility is set to Team.
2. From App Details, click Publish.
3. Notis reads the listing metadata from the deployed manifest and pushes the listing to your team’s store.

There’s no review step for team listings — they go live immediately. Click Update later to push a new version (after another notis apps deploy).

​

Publish to the public store

1. Make sure visibility is set to Public.
2. From App Details, click Publish.
3. Notis opens a GitHub Pull Request against the public catalog with your listing metadata and a pointer to the deployed bundle.
4. The Notis team reviews the submission for safety, quality, and store guidelines.
5. Once approved and merged, the listing goes live in the public App Store.

​

Submission lifecycle

You can track active and historical submissions on the App Details page, in the Submissions section:

• Pending review — your submission is waiting for the Notis team.
• Approved & merged — live in the public store.
• Changes requested — fix the noted issues, run notis apps deploy, then publish again.
• Rejected — see the reviewer’s note. You can iterate and resubmit.

​

Withdraw a pending submission

If you spot an issue or want to ship a different version, open the submission row and click Withdraw. The PR is closed and the submission is moved to the Withdrawn state. You can publish again at any time.

​

Update an existing listing

After making changes and running notis apps deploy, head back to App Details and click Update. The same publish flow runs — instant for team listings, a new PR for public listings. Existing installs of your app see the Update available indicator and can apply the new version cleanly or resolve conflicts with Notis’s help. See Install apps from the store → Update an installed app.

​

Unpublish

From the ⋯ menu on App Details:

• Team listings — instantly archived. Existing installs keep working but new installs are disabled.
• Public listings — opens a removal PR against the public catalog. Once merged, the listing is taken down. Existing installs keep working.

Unpublishing does not delete the app from your workspace, nor from anyone who already installed it.

​

Tool boundary recap

The portal never deploys code, and the CLI never publishes listings. Each surface owns its lane.

​

Related

• Overview — what apps are.
• With Notis — the chat path.
• With your coding agent — the developer path.
• Install — the install side of the lifecycle.
• Sync Integrations — the Notis CLI path for local agents.