Configure project settings and domain authority
Update a project’s general, contact, AI, and domain settings while preserving deployment and authority boundaries.
3 min read
- Project
- Settings
- General
Project name, website domain, allowed domains, and authority confirmation are on the General tab of project Settings.
Open the target project and go to Settings. The tabs separate general deployment settings, contact details, AI & Prompts, and Privacy. Changes apply to the selected project only, so check the project name and domain before saving.
Separate where the widget may run from your authority over the primary website. Update one settings area at a time, then verify it on the intended deployment.
- Finish with
- A correctly scoped project configuration and domain boundary
Update general and domain settings
Review the selected projectIn Settings → General, check name, primary domain, description, allowed domains, and activation.
Changes apply only to this project.Set the deployment boundaryEnter clean host names for every intended widget location.
Keep the primary domain in the allowed-domain list.Attest and testConfirm authority when the primary domain changes, save, then test the installed widget.
Primary-domain authority does not grant crawl authority for URL sources.
The authority confirmation is recorded for the project domain. It is required when creating a project and when its primary domain changes. It does not establish permission to crawl every URL: URL knowledge sources have their own authority confirmation in the knowledge workflow.
Update contact and AI settings
Set visitor contact pathsAdd only the phone, WhatsApp, email, and support URL visitors should receive.
Keep contact details current and project specific.Keep AI guidance groundedReview instructions and business context for the selected project.
Include its products, policies, and escalation path—not generic assumptions.Save and retestSave each tab independently, then test representative and out-of-scope questions.
Confirm prompt changes do not overpromise.
Limitations
- Domain authority is an attestation, not domain ownership verification and not a transfer of rights to third-party content.
- Allowed domains protect where the widget can run; they do not authorize data sources, integrations, or external actions.
- Available AI controls depend on the project’s current availability. Do not copy an option from another project assuming it will be available here.
Last updated on
Manage projects, workspaces, and roles
Understand project scope, workspace membership, role boundaries, and the agreement required for project creation.
Review billing and project usage
Use the project Billing page to review current plan availability, billing-cycle usage, knowledge capacity, and add-ons.