Security
Security controls follow the post from sign-in to final publication.
Atlas Verve AI combines identity, ownership checks, protected connections and explicit approval so automation does not become silent publication. This page explains the controls users and administrators can expect.
Overview
A practical, layered control model
No single link or background task is trusted on its own. The application checks identity, post ownership, signed requests and current workflow state before a publication decision can advance.
Secure sign-in
Email/password and Google sign-in use one protected account service. Administrator access must be assigned separately; it is never granted just because of an email domain or sign-in method.
Protected LinkedIn access
LinkedIn asks you to approve access before Atlas Verve connects. Connection credentials are encrypted and are never displayed back to users.
Browser and abuse protection
Sign-in, generation, approval and publishing requests are limited to reduce abuse. Encrypted connections and browser safeguards reduce common risks.
The workflow
Controls across the content lifecycle
Each layer addresses a different risk instead of relying on a single gate.
-
01
Authenticated workspace
Private dashboards, drafts, settings and post records require a valid session.
-
02
Owner-scoped data
Users work with their own topics, drafts, schedules and publishing connections. Administrative functions require a separate role.
-
03
Protected actions
Forms and approval links include safeguards that prevent another site or an altered link from submitting actions on your behalf.
-
04
Explicit approval
The review page confirms both identity and ownership before it accepts an approval decision.
-
05
Conservative failure handling
Ambiguous delivery is marked for investigation. The system does not blindly repeat a request when duplicate publication might be possible.
01
Public and private search boundaries
Only public product and guide pages can appear in search results. Sign-in, approvals, workspaces, posts, settings, administration and private media are excluded from search crawling.
02
Sensitive service details
Sensitive connection details are kept outside the application source and are never shown in the workspace.
03
What users still control
Users should protect their sign-in and LinkedIn accounts, review destination access regularly and avoid approving content they have not read.
Common questions
Clear answers before you begin.
Does Google sign-in automatically make someone an administrator?
No. Administrative access must be assigned separately to the account.
Can an approval email be forwarded to publish a post?
No. The review flow verifies the authenticated post owner and requires an explicit decision.
Are private post pages listed in the sitemap?
No. The sitemap contains only public marketing and educational pages.