Understanding Projects — A-Stats Docs

Why Projects Exist

Every piece of content in A-Stats lives inside a project. Projects keep your work organized by giving each website, client, or content program its own isolated workspace — with its own articles, brand voice, integrations, analytics, and team members.

A solo creator might use one project for their blog. An agency creates a separate project per client. A marketing team might split projects by brand or campaign.

What Each Project Includes

| Feature | How It Helps | |---|---| | Brand Voice | AI-generated content matches the tone, style, and terminology for that specific project | | Knowledge Vault | Uploaded documents are scoped to the project — one client's brand docs don't bleed into another's content | | Integrations | Each project connects to its own WordPress site, Google Search Console property, and social accounts | | Team Members | Invite people with specific roles — they only see the projects they belong to | | Analytics | Search performance, content health alerts, and usage data are all project-scoped |

Team Roles

Each project supports four roles so the right people have the right level of access:

| Role | What They Can Do | |---|---| | Owner | Full control — billing, settings, deletion, role management | | Admin | Manage team members, configure settings, create and edit all content | | Editor | Create and edit articles, outlines, images, and social posts | | Viewer | Read-only access to all content and analytics |

Roles are per-project. Someone can be an Admin on one project and a Viewer on another.

Built for Scale

Projects are free to create. Your subscription limits apply at the account level, not per project — so you can organize your work however makes sense without worrying about artificial constraints.

Projects are available on all plans. Free accounts include 1 project. Paid plans include 3 to unlimited projects depending on the tier.