Security & Control
Agency social operations
Explicit approvals, separated projects, activity records, and visible AI usage.
Separation and evidence
Client work stays where it belongs, and the record says what happened.
Each client's work lives in its own project. Connected accounts, drafts, galleries, approval states and publishing history belong to that project, so the boundary an agency is accountable for is the boundary the workspace uses.
Approval is an explicit state rather than an assumption: pending, approved and rejected are recorded decisions, and a post reaches a channel because someone approved it. Activity and AI usage are recorded alongside the work, so a team can answer what was generated, what was published, and who moved it forward. These are product behaviours, not certifications, audits or compliance attestations, and this site claims none.
- 01
Separated by project
A client's accounts, posts and assets stay inside that client's project.
- 02
Approval as a state
Pending, approved and rejected are recorded decisions, not implied ones.
- 03
Activity on the record
Generation, scheduling and publishing stay inspectable after the fact.
Operating principles
Automation should remove tab switching, not responsibility.
01
AI drafts the first pass. Your team still owns the brief, the edit, the approval, and the moment it goes live.
02
A calendar becomes useful when it shows every client, every state, and the decision that comes next.
03
The system records activity and usage so speed does not come at the cost of accountability.
About control
What the platform records, and what it does not claim.
How is client work separated?
Each client's connected accounts, posts, gallery, status and performance context sit inside that client's project, within the agency's own workspace.
Can a post reach a channel without an approval?
No. Approval is an explicit recorded state, and scheduling and publishing follow it rather than replace it.
What activity is recorded?
The platform records generation, approval, scheduling and publishing activity alongside the project it happened in, together with AI usage.
Does Social Engine hold a security certification?
This site makes no certification, audit or compliance claim. What is described here is how the product behaves; anything beyond that would need to come from BT Web Group in writing.
Who holds account and payment data?
Marketing Hub does. This site presents no login form, accepts no credential, and stores nothing about a visitor.
Next command
Human approval before publishReplace the tool chain with one visible publishing path.
Create your Marketing Hub account and set up the first client project. Account creation, payment and billing are handled inside the application.
Create your account