When more than one person touches a social account, or when you post for clients, you need to know who can publish, who checks the work and what was done. LAS AutoPost has roles, an approval queue, an audit log and printable client reports for exactly this. This guide explains how each piece works and how to set them up for a small team or an agency.
One workspace per client
A workspace holds everything for one brand: its destinations, feeds, queue, Brand Brain, analytics and reports. A person can belong to several workspaces and switch between them in the header. Agencies should create one workspace per client, so one client's channels, team and plan are never mixed with another's. Each workspace has its own plan, so a client you manage on the Free plan does not need to use up the Agency limits.
Roles
Access is controlled by five roles, enforced on every page and denied by default:
| Role | What they can do |
|---|---|
| Viewer | Read only |
| Contributor | Write posts and clips, which go to approval |
| Editor | Publish, approve, manage feeds, the queue and video |
| Admin | Everything an editor can do, plus destinations, integrations, team, audit log and viewing billing |
| Owner | Everything, including billing changes and deleting the workspace |
The global emergency stop is available only to the platform owner. The number of people you can invite depends on the plan: 1 seat on Free, 3 on Pro and 10 on Agency.
Inviting people
Invite a teammate by email from the Team page. The invitation is a single-use link that works for seven days and can only be used by the invited email address. If email delivery is not configured, the Team page shows you a link you can copy and send yourself.
How approvals work
A contributor's posts and video clips do not publish. They wait in Approvals, where an editor can approve, reject, comment, or let the contributor withdraw the item. You can switch on a two-step approval: first an editor, then a different admin. AI-written captions that a feed produces in "suggest" mode are kept on the separate Drafts page. Every decision, with who made it and when, goes into the audit log.
A good practice for client work: give the client's staff the Contributor role so that they can propose posts, and keep Editor for your own team. The client sees their ideas appear in your queue, and nothing goes out without a check.
The audit log
Admins can open the Audit log to see logins, destination changes, publishes, approvals, invites, settings, billing events and exports, with filters and a CSV export. Secrets are never written to it. Entries are kept for 400 days. If a client asks "who posted that and when?", the answer is a search away.
Client reports
Under Reports, each month has a printable report built from the workspace's analytics. It uses the Brand Brain's brand name, logo and colours, so it looks like it comes from the client's brand or from yours. To send it, use the browser's Print, then Save as PDF. The numbers come from AutoPost's own tracked links and the platforms' metrics. Where a platform does not allow a metric to be read, the report shows it as unavailable rather than guessing.
Safety switches that help a team
- Pause a workspace to stop all publishing at once.
- Use dry-run mode to test a new setup without posting.
- Per-destination daily caps stop a mistake from becoming a flood.
- Duplicate protection prevents the same post going to the same channel twice.
Setting up an agency client in ten minutes
- Create the workspace and name it for the client.
- Fill in the Brand Brain: voice, audience, banned words, hashtags and call to action.
- Connect the destinations. The client may need to authorise some networks themselves.
- Invite the client as a Contributor and your team as Editors.
- Add the client's blog feed and set the AI caption to Suggest.
- At month end, open Reports and save the PDF.
See also How to turn an RSS feed into scheduled social posts and the LAS AutoPost overview.
Written by Lawal Ayo. Spotted something out of date? Tell us and we will fix it. See our editorial standards.