Account
Projects
Every field on the project record, who is actually allowed to change it, and what pausing and archiving really do.

What's scoped to a project, and what isn't
A project is one website you're tracking, and it is the boundary almost
everything else in this section hangs off: a team roster, a set of keywords
and tags, an activity log, and the exports you can download are each read
back by project id and belong to exactly one project
(api/routers/team.py#list_members, api/routers/keywords.py#list_keywords,
api/routers/tags.py#list_tags, api/routers/pages.py#get_activity_page,
api/routers/exports.py#exports_index). Two things sit above a project.
Its company holds the plan, the billing and the company's members, and
every project in the company draws on that one plan; a project belongs to
exactly one company (api/services/plan.py#get_project_plan). You hold
your sign-in details and the Google account you connect for Search Console
and Analytics. That last one is worth being exact about: the connection is
found by your user id with no project in the query at all, and which Search
Console or Analytics property feeds which project is a separate mapping
underneath it (api/services/integrations/google/oauth.py#get_active_integration).
The navigation follows the same three levels. Project settings covers
the project you have open, in four groups: Project (Project, Team, Plan and
usage, Activity), Tracking (Brands, Personas, Variant templates, Keywords,
Tags), Connections (WordPress, Crawler logs, API keys) and Data (Exports)
(frontend/src/routes/(app)/settings/+layout.svelte#groups). The company's
own pages, Billing, Members, Projects and General at
/companies/<id>/..., are for its members only. And
Your profile
holds your name, your companies, your sign-in and the Google connection,
whose page maps properties into any project you can write to; see
Integrations. See
Plans and limits for what the company
means for billing specifically.
The project record
The record itself, and everything on it, is one form
(frontend/src/lib/components/ProjectRecordForm.svelte) on the settings
screen of the project you currently have selected; the company's Projects
page, further down this page, opens another project's settings by switching
to that project first. The form posts every field it
shows, so if the country, business type or language list fails to load, it
is held back with Retry rather than shown: saving without one of those
lists would clear that field
(frontend/src/lib/components/ProjectRecordForm.svelte#listsMissing).
Identity: a required project name, and a website field that is shown but can
never be changed once the project exists, because every domain, citation and
snapshot the product has collected is tied to that original URL. Beneath
those, a business type chosen from a fixed list of verticals, and a free-text
description of what you sell. All four, plus the business goal described
next, are read together as the project's business identity by the agents
that write on your behalf, most directly Growth Advisor's and the llms.txt
Advisor's own research step (api/services/growth_advisor.py#_business_block,
api/services/llms_txt/service.py#_business_block). A default language sits
with them: the language new prompts use, "As written" unless you pick one,
and changing it leaves existing prompts as they are (see
Languages and templates).
Business goal is the same idea taken further: a plain-English statement of
what the business is trying to achieve, which every one of five separate
agent runs reads as steering context rather than as an instruction to
follow literally: the Growth Advisor's
briefing, the llms.txt Advisor's audit,
Optimizations's recommendations,
Articles's drafts, and the research pass behind
Prompt suggestions
all read it (api/services/growth_advisor.py#_business_block,
api/services/llms_txt/service.py#_business_block,
api/services/optimization/service.py#generate_recommendation_for_opportunity,
api/services/article_writer/corpus.py#project_payload,
api/services/research.py#run_pipeline). The business type also doubles as
the fixed set of options a research pass can choose between when proposing
one for you during setup (api/services/research.py#business_profile_schema).
Generate a description and goal from your website
Company members can select Generate from website above the description and business goal fields. The background job reads the homepage and up to four relevant pages on the same website, then uses Codex to draft both fields. It uses the description and goal currently in your form as context, including edits you have not saved yet.
The preview shows a factual description, a suggested business goal, any caveats, and the source pages. A website cannot establish your internal targets, so check that the proposed goal matches your priorities. If the site does not provide enough evidence, generation reports that instead of filling in guesses.
Choose Use description, Use goal, or Use both to replace those fields in the form. You can edit the text before selecting Save changes. Generating or previewing a draft does not save settings, and edits made while generation is running stay in place until you choose to use a draft.
The latest draft and its status are available when you return to the settings page. A failed job offers Try again; repeated requests have a short cooldown. Editors and viewers cannot generate settings drafts.
Other project settings
Target countries: a checkbox per seeded country, opening with the countries
this project already has ticked, since the form is initialised from the
project's own current set (frontend/src/lib/components/ProjectRecordForm.svelte#initial).
That set is never empty on a project created through onboarding, which
refuses to create one with no country at all
(api/routers/projects.py#create_onboarding_project).
Every country you add is tracked as its own separate set of prompt
executions, so more countries draw on the same pooled capacity a prompt
itself does; see Plans and limits for what
that capacity is and how it's shared. There is no separate cap on how many
countries you can pick beyond that.
Tracking: a toggle to run the project at all, covered in the next section,
and a toggle for whether a weekly pass re-runs prompt discovery and proposes
new prompts on its own. Turning the weekly pass on can be refused depending
on your plan; turning it back off is always allowed
(api/routers/projects.py#update_project). Its results land on
Prompt suggestions.
Report branding: an accent colour and a logo URL, both optional, both
validated as a real six-digit hex colour and a real https:// link before
they're accepted (api/schemas/project.py#validate_brand_accent,
api/schemas/project.py#validate_brand_logo_url). Neither is read by any
agent. The accent colours the printable
Weekly report and every new
client report link, which keeps the colour
it was captured with; the logo appears only on the printable report. With
no accent set, both use coral, #F2685C, and the printable report shows no
logo when that field is empty
(frontend/src/routes/(app)/insights/report/+page.svelte#accent,
frontend/src/lib/report-accent.js#REPORT_ACCENT_DEFAULT,
api/services/report_shares.py#DEFAULT_REPORT_ACCENT).
Who can open and change it
Opening this screen and saving from it are two separate permissions, and only the second one is for company members alone.
The request that loads the project record accepts a member of the project's
company or anyone holding an active project row on it, whatever their role,
which is the same rule the rest of the product's project-scoped reads use
(api/routers/projects.py#get_project, #_accessible_to,
api/dependencies.py#get_project_for_user). An editor or viewer you added
can open the form and read what is on it.
Saving is refused for anyone but a member of the project's company: the
endpoint behind the Save button reads the caller's role and accepts only
owner, the role a company member holds on every project of the company
and nobody else can hold (api/routers/projects.py#update_project,
api/dependencies.py#get_user_role_in_project). Adding or removing a social
account, covered below, and archiving the project carry that identical
check (api/routers/growth_advisor.py#add_social_profile,
api/routers/projects.py#delete_project).
The screen and the API agree about who may edit, and this is not special to
the project record: the same isOwner test, reading the project's
my_role, gates every company-member-only control across the app
(frontend/src/lib/permissions.js#isOwner). Here it is handed to the form
rather than a broader write test, so an editor or viewer sees the fields as
read-only with a short line saying why, instead of a Save button whose
request the API would refuse
(frontend/src/routes/(app)/settings/+page.svelte#isOwner,
frontend/src/lib/components/ProjectRecordForm.svelte#canSave). The Archive
control is gated the same way, exactly as its endpoint is
(frontend/src/routes/(app)/settings/+page.svelte#canArchive). An editor's
or viewer's role otherwise governs what they can do elsewhere in the
product, on prompts, competitors, keywords and tags, where editors do have
write access.
Pause, and archive
"Run this project" and "Archive this project" end up doing the exact same
thing to your data: both simply set the project's own active flag to off,
and nothing else is removed, touched, or queued for removal
(api/routers/projects.py#update_project, api/routers/projects.py#delete_project).
Turning a project off, by either route, is what actually stops anything from
happening to it: every scheduled pass, the daily run included, only picks up
projects whose flag is still on (api/tasks.py#_enqueue_for_company), and a
paused project's active prompts stop drawing on the company's pooled
capacity the moment it's off
(api/services/limits.py#get_active_prompt_slot_count).
Turning it back on re-runs the same check that creating a brand new project
would; see Plans and limits for what that
re-check does. The visible difference between the two controls is entirely
in the interface: the toggle flips with one click, while Archive opens a
dialog that asks first and, if the request is refused, shows why and stays
open rather than navigating away regardless
(frontend/src/routes/(app)/settings/+page.server.js#archiveProject). That
control used to be called "Delete this project" and to arm only after you
typed the project's own name, which framed as irreversible something the
API never made irreversible. An archived project still appears, as a paused
project, on the company's Projects page below, with the same Resume button
any other paused project has.
A company's projects
A company's Projects page, /companies/<id>/projects, lists every
project in the company, paused and archived ones included, and only the
company's members can open it (api/routers/companies.py#list_company_projects,
api/dependencies.py#get_company_for_member). Each row shows the project's
name, its site, whether it is active or paused, and how many prompt slots it
uses from the company's pool; the header shows the company's active
projects against its plan's limit, paused ones not counted. From a row a
member can pause or resume the project,
with the same toggle described above and the same re-check on resume, or
choose Open settings, which switches the current project to that one
and opens its settings, so there is one settings screen rather than a
second copy of it. New project opens setup with this company already
chosen; see Onboarding.
At the plan's project limit it gives way to a link to the company's Billing
page (frontend/src/routes/(app)/companies/[id]/projects/+page.svelte#canCreate).
Projects shared with you as an editor or a viewer are not on any company
page. They appear in the project switcher, grouped under their company, and
on Your profile,
where you can leave one. The switcher and the redirect that sends a person
with no projects to onboarding both read the same list as every other
project request: the projects of every company you are a member of, plus
those where you hold an active project row
(api/routers/projects.py#list_projects, #_accessible_to). The old
Settings → All projects address now sends a company member to the current
project's company Projects page, and anyone else to Your profile
(frontend/src/lib/company.js#projectsRedirectPath).
Keywords and tags have their own tabs under Project settings, and the settings screen for your selected project links to them with a count of each, under Prompt labels; competitors are added, paused and removed on the Brands tab (see Brands and sub-brands).
Social accounts
A project can list its own public social profiles, one platform picked from
a fixed set and a URL, no login involved. The Growth Advisor reads these
alongside its other research to judge how the business is doing on its own
channels (api/services/growth_advisor.py#build_research_prompt). A project
can hold at most ten of them, checked on the server regardless of what the
form shows (api/routers/growth_advisor.py#MAX_SOCIAL_PROFILES). Adding and
removing one both carry the same company-member check as the rest of this
screen. When the list cannot be loaded, the section says so with Retry,
its count shows a dash rather than 0, and neither adding nor removing is
offered over a list the screen never saw
(frontend/src/routes/(app)/settings/+page.svelte#socialFailed).
The platform picked here is only a label for this list; it plays no part in Social sources, where a saved profile's network and account are read straight from its URL, so a profile saved under the wrong platform still labels its citations correctly there.
Admin read-only view
Platform admins can choose Open read-only beside a project in
/admin/projects. This opens the regular app with that project fixed as the
selection and viewer permissions. The admin keeps their own identity; no
customer login or team membership is created.
The banner names the project and provides Return to admin. Returning ends the support session and restores the admin's original project selection. The session expires after 30 minutes. Expiry locks further access until the admin returns and opens a new session; it never enables editing automatically. App tabs in the same browser share this mode.
The API restricts access to the selected project and approved read operations,
and uses a read-only database connection. Saving, generating, rerunning,
publishing and deleting are blocked. Your profile, the company pages
including billing, credentials, sharing and tools requiring additional
operations are unavailable in this mode. Session start and end are recorded in the project's activity log under
the real admin's identity (api/routers/support_view.py#start_support_view,
api/routers/support_view.py#end_session,
api/dependencies.py#enforce_support_view).
Related
- Plans and limits: the project-count ceiling this page's toggle and resume both re-check, and how prompt capacity pools across every project in a company
- Team: company members, project editors and viewers, and what each can change here
- Create your account: how sign-in works and how your first company and project come to exist
- Onboarding: where a project's name, business type, description and countries are first filled in
- Growth Advisor: the weekly briefing that reads this project's business identity and social accounts together
- Social sources: which AI-cited accounts these profiles label as yours, and how a competitor's accounts are added
Last verified 2026-10-14