Client review workflow: approvals without GitHub access
Letting clients approve content shouldn't mean giving them GitHub access. Acrosite gives Client Reviewers an account-based, review-only experience for their assigned content, with comments, approval, and request-changes — separate from your repository and settings.
May rely on email, docs, or shared logins to collect client approvals on content.
May fit teams that want a dedicated, review-only experience for Client Reviewers without GitHub access.
The right choice depends on whether you want ad hoc approvals or a structured client review workflow.
Ad hoc review and Acrosite, compared
Approaches differ by team and setup — verify current specifics against each tool's documentation.
This is a high-level workflow comparison. The right fit depends on your website setup, team workflow, and publishing requirements.
What changes in the workflow?
- 01Content is shared with clients by email or docs.
- 02Feedback comes back across several channels.
- 03Someone manually tracks approvals and applies changes.
- 01The team creates Posts, Pages, and Custom Content Types.
- 02Writers and editors work without GitHub access.
- 03Client Reviewers can review their assigned content.
- 04Approved content can be scheduled.
- 05Acrosite commits to GitHub and records Publish Logs.
When should you choose which?
Publishing operations, built in
Review workflow
Move content through review and approval before publishing.
Scheduled publishing
Schedule approved content with date, time, and timezone.
GitHub publishing
Acrosite commits content to your connected repository.
Publish Logs
See trigger results and recovery context for each publish.
Client Reviewers
Clients review assigned content without GitHub access.
Posts, Pages & Custom Content Types
Model the content you publish across projects.
Custom Fields
Add the fields each content type needs.
Team Members
Give your team publishing roles without repository access.
Common questions
Client Reviewers get an account-based, review-only experience scoped to the content assigned to them.
No. Client Reviewers do not see GitHub, billing, deployment triggers, or internal project settings.
No by default. Client Reviewers can comment, approve, or request changes. Publishing is controlled by authorized internal roles.
For a single one-off approval with no ongoing workflow, a quick email or doc may be enough.
Try a simpler Git-backed publishing workflow.
Registration is coming soon. Contact us to talk through your publishing workflow, or read the docs to see how Acrosite works.