Content Signal treats tenant boundaries, credentials, approvals, and audit history as product requirements, not deployment footnotes.
Access is granted through organization membership and role checks.
Risky SEO operations stay behind a visible human confirmation step.
Supported write fields capture prior state for restoration workflows.
Critical activity is recorded with tenant, actor, state, and outcome context.
The list below describes controls present in the product today. Enterprise SSO and a formal compliance package remain roadmap items and are not represented as complete.
Every organization-scoped read and mutation verifies membership. Seven roles (Owner, Admin, SEO Manager, Editor, Writer, Billing Manager, Viewer) constrain sensitive actions, and a member's access can be scoped down to specific sites.
Google refresh tokens, WordPress apply tokens, and TOTP secrets are encrypted before database persistence.
Users can enroll an authenticator app. Login verification prevents reuse of an already accepted TOTP counter.
Supported changes require preview, validation, dry run, explicit confirmation, signed execution, and a recorded result.
Membership, connections, tasks, billing, and bulk operation activity remains associated with organization and actor context.
CI runs dependency auditing and CodeQL analysis alongside linting, tests, builds, database migration verification, and PHP checks.
A disposable-database smoke workflow validates that PostgreSQL backups can be restored and migration history can be read.
Queue payloads carry tenant scope, use deterministic job identifiers where needed, and expose failure and lag signals for operations.
Do not include credentials, customer content, or active exploit details in a public issue. Use the demo contact form and select “Security review” so the report can be routed privately.
Contact securityWe will distinguish implemented controls from roadmap items and walk through the review-first operation flow.