How it works
Organizations, projects, pages, reviews, sharing access, permissions, and safe rendering.
TrayPage is a workspace for reviewing AI-generated HTML / Markdown pages with a team and turning comments into the next version. In normal use, the important concepts are organizations, projects, pages, versions, and sharing access.
Where pages live
Pages are stored inside projects, and projects belong to organizations.
- Organization — A personal or team workspace. After first sign-in, TrayPage creates your Personal organization and default project automatically. Team organizations are created explicitly. Members, billing, and allowed-domain settings are managed at the organization level. During the beta, each newly created organization receives a one-month Pro trial automatically.
- Project — A place to group pages. Each project can define the default sharing access for new pages.
- Page — An AI-generated HTML / Markdown deliverable. A page has a title, share link, sharing access, comments, and version history.
- Version — A saved revision of a page. TrayPage does not rewrite older content in place; each revision is added as a new version.
For individual use, start with the Personal organization and default project created after first sign-in. For team use, create a team organization and organize pages by project.
Review flow
The core TrayPage loop is: AI creates → the team reviews → AI revises.
- The AI agent publishes a page as a draft
- Team members review it in the browser and comment on the relevant text
- When review is done, the revision instructions are sent back to the AI agent
- The AI agent publishes a new version with the comments applied
- After checking the result, publish the version that should appear from the share link
With the CLI, a waiting AI agent can resume automatically when the reviewer marks the browser review complete. In a manual flow, use Copy revision prompt in the browser to copy the instructions for the AI.
Each page has a latest version and one live version shown to shared viewers. Adding a new draft does not change the share link output until you publish that version. Only one version can be live at a time.
Sharing Access
Sharing access controls who can view the page body from the share link. It can be changed per page and starts from the project default.
| Sharing access | Who can view |
|---|---|
| Private | Only people explicitly added |
| Project Members | Members of that project |
| Company Domain Users | Signed-in users on allowed company domains |
| Anyone with the link | Anyone who opens the share link, without an account |
Anyone with the link is view-only. Anonymous viewers do not see comment controls. To comment, a viewer must sign in and must be included in the page's sharing access.
Wider sharing access means more people can view the page. Before external sharing, check the sharing dialog for the current access setting and share link.
Permissions
TrayPage combines organization/project membership with page-specific sharing.
- Viewer — Can view and comment on pages.
- Editor — Can add new versions and work through review comments.
- Admin — Can publish versions, change sharing access, and manage individual shares.
Normal team operations are determined by organization and project membership. To share just one page with a different person, add them from the page sharing dialog. For the full matrix, see the Permission reference.
Safe Rendering
Published HTML is rendered separately from the TrayPage app. This keeps page scripts from touching your TrayPage session or organization/project data.
- The review screen shows page content inside an isolated preview
- In production, page content is served from a separate rendering area from the app itself
- External API calls, embeds, and forms can work, while browser-managed persistent storage stays unavailable
For details on what page content can use, see HTML capabilities.