Content manager
The content workspace is how a branch appears in Reels — the short-video feed guests scroll in the Sitora app.
The tabs
Section titled “The tabs”| Tab | What it holds |
|---|---|
| Reels | The branch’s video library |
| Comments | Comments waiting for moderation |
| Stats | How the content is performing |
Content work is branch-scoped, like everything else in Sitora Pro, and the app says so before it lets you start: “content work is always branch-scoped. Choose the active branch before managing reels, comments, or statistics.”
There is a second scope, and it is not automatic. When you upload, you choose whether the reel is Branch-level — “this branch” — or Restaurant-level — “the whole restaurant”. Restaurant-level needs an explicit restaurant publishing grant. Without it the option is there but marked “restaurant-level needs an explicit grant”, and a restaurant-level reel already published is one you cannot change: “restaurant-level reels need an explicit restaurant publishing grant to change.”
Your library, filtered by state:
| State | Meaning |
|---|---|
| Published | Live, and guests can see it |
| Drafts | Uploaded, not published |
| Hidden | Was published, now withdrawn |
| Archived | Retired from the library |
Counters across the top show published, drafts, hidden, views today, views over 7 days, and subscribers.
Publishing
Section titled “Publishing”Upload a new reel, add a caption, and publish.
Actions on an existing reel:
- Publish — a draft goes live
- Hide — withdraw it from the feed
- Republish — put a hidden one back
- Archive — retire it
Comments
Section titled “Comments”Comments guests have left, per reel, and three actions on them.
Remove. The comment leaves the public thread. It is not destroyed — “it can be restored later” — and a removed comment is labelled in the thread as Removed by moderation, distinct from Removed by author. Show removed comments brings them back into view for you without putting them back in public.
Restore. Puts it back: “the comment returns to the public thread.”
Reply as business. You can answer a commenter, or comment on your own reel, under the business name rather than your own. The sheet is explicit: “the answer is posted publicly under the business name.” Those replies are marked in the thread as a Business comment, so a guest can tell the restaurant from another guest.
All three ask you to press and hold, because all three are public acts.
Moderation is the branch’s call. Sitora does not decide what belongs under your reel; you do. Two habits worth keeping:
- Remove abuse quickly. A comment section nobody tends stops being useful.
- Answer questions. A guest asking “do you do this without nuts” in a comment is a customer talking to you — and Reply as business is how the answer gets the restaurant’s name on it.
Performance over 7 days, 30 days or 90 days:
| Number | What it means |
|---|---|
| Views | Times a reel was watched |
| Watch time | Total time spent watching |
| Likes | Likes received |
| Subs gained | New subscribers in the period |
| Subs total | Subscribers overall |
Watch time is the number worth watching most. A reel with many views and little watch time was scrolled past; one with fewer views and long watch time held attention — and that is the one to make more of.
Day-to-day recipes
Section titled “Day-to-day recipes”We have a new dish and want it seen. Publish a short reel of it being made or plated. Then make sure the dish is actually available and correctly priced at this branch — a reel driving orders for something switched off is worse than no reel.
A comment is abusive. Hide it. You do not owe it a reply.
An old reel shows a dish we no longer serve. Hide or archive it. Guests do act on these.
Nothing is loading. Content actions are online only. Check the status strip and reconnect.
I switched role and the workspace closed. Expected — the content workspace only runs while your active role is content manager. Switch back.
What a content manager cannot do
Section titled “What a content manager cannot do”- Change the menu, prices or availability. Branch admin or storekeeper.
- See or change orders, payments or stock.
- Publish for another branch. Switch branch.
- Act while offline.