What Acrosite stores about your content
An overview of the workspace-scoped records Acrosite keeps — drafts, structure, media references, review and publishing history, and logs — and what stays in your repository.
Acrosite keeps a workspace-scoped record of your content work so your team can write, review, schedule, and publish. Your published content also lives in your own repository. This reference summarises what Acrosite stores and where.
Who this is for
Workspace Owners who want a clear picture of what data Acrosite holds.
What Acrosite stores in the workspace
Inside your workspace, Acrosite keeps the records that make authoring work:
- Drafts and content items — your work in progress and its current status.
- Content structure — your Custom Content Types and Custom Fields.
- Media references — the staged and published media for your projects.
- Review history — submissions, approvals, requested changes, and comments.
- Publishing and deployment records — Publish Logs and Deployment Logs (sanitized).
- Workspace and billing state — your team, plan, usage, and access state.
All of this is scoped to your workspace. See Workspace and tenant isolation.
What lives in your repository
When you publish, your content is committed to your own GitHub repository as Markdown with frontmatter, along with the media it uses. That repository is the source of truth for your published site. See You own your content and repository.