Full Configuration

Full Configuration is the deepest of Horizon’s three onboarding flows: company profile, departments, every platform connected, and the Navigator running. It takes 1–2 hours, and this page also covers the settings that live outside the flow.

Caution

This page has been corrected. Several sections described features that do not exist. If you acted on any of the following, this is why it did not work:

• Webhooks are inbound, not outbound. Horizon does not push events to your endpoint, and there is no event catalog to subscribe to. A receiver you built for conversation.completed, skill.executed, connection.status_changed or job.completed will never be called — none of those event names exist.
• API keys do not have read / write / admin scopes. New keys carry a per-feature permission matrix and an optional board scope.
• “Manager” and “Viewer” are not roles. The real set is listed below.
• An organization has exactly one wallet. You cannot create per-department or per-project wallets. Department spend is controlled with a department budget.
• There is no CSV bulk invite.

Before you start

Complete the Quick Start first.

The guided flow

Horizon presents onboarding at /onboarding under Welcome to Horizon, offering Quick Start (~15 min), Industry Setup (~30 min) and Full Configuration (1–2 hours). The Full Configuration flow walks four steps: company profile → departments → connect platforms → Navigator.

The rest of this page covers the same ground from the left rail, plus the settings the flow does not touch.

Company profile

Company > Profile holds the strategic context agents reason with — not a contact card. The profile carries your company name, industry, company size, founded year, core values, niche, ideal customer profile and geographic focus, plus one-year and three-year targets plus financial targets (annual revenue target, monthly burn, target gross margin, DSO and DPO, funding stage, runway).

Tip

Write the niche and ideal customer profile the way you would explain the business to a new employee. Agents use them as grounding context.

Goals

Company > Goals holds objectives agents reference when they report and recommend. A goal has a title, description, type (yearly by default), owner, measurables, status, and a start and end date. Goals can nest under a parent goal, so an annual objective can carry quarterly children.

Organization settings

Settings opens on General, which carries the organization name, a description, the Operator toggle (on by default), and multi-entity separation.

Settings is a tab strip: General, Users, Roles, Guest Access, Partners, API Keys, Notifications, Finance, Payments.

Caution

The Partners tab is currently broken — it has no page behind it and lands on the 404. Tracked in horizon-app#3224.

Roles and users

1. Review the roles

   Horizon ships seven built-in roles:

   Role
   owner	Granted only through the dedicated assign-owner path, never a dropdown
   admin
   department_lead
   member
   billing_admin
   controller
   accountant

   Every role except owner is offered in the invite and role-assignment dropdowns.

2. Invite people

   Go to Settings > Users and select Invite User. Enter an email address and pick a role.

   Invite one person at a time — there is no CSV import.

3. Grant guest access

   Settings > Guest Access controls whether people outside the organization can be given board-scoped access, and caps how many guests a board may have.

Departments

Go to Workspace > Departments and select Create Department. A department has a name and a description, and holds the agents and connections its members work with. Departments scope agent context and control who sees what.

Connections

Go to Workspace > Connections and select Connect Service. Each service connects by OAuth, by API key, or by service-specific credentials.

• QuickBooks
• Sage Intacct
• Salesforce
• HubSpot
• Slack
• Microsoft 365
• Google Workspace
• Jira

A healthy connection shows Active. If a connection breaks, any agent skill depending on it stops working — the Connections page flags those skills so you can point them at a replacement connection.

Apps and agents

1. Deploy apps

   Store > Apps carries the app catalog; the Store also has Agents, Skills and Community. The catalog is per-environment, so browse it rather than going by a list.

2. Customize agent instructions

   Workspace > Agents holds your deployed agents. Add your terminology, reporting preferences, and escalation rules — see Building agents > instructions.

3. Assign agents to departments

   Back in Workspace > Departments, check each department has the agents its people need.

Company features

The Company group holds Profile, Goals, Boards, Altitude Checks, Navigator, Notifications and Core Offering.

• Boards — task boards. They are also the unit of scope for guest access and for API keys.
• Navigator — the agent that watches the business against your goals.
• Altitude Checks — periodic reviews the Navigator generates for a date range: a scorecard, milestone review, issues, wins, recommended actions and an executive summary, delivered on a channel you choose.
• Notifications — organization-level notification settings. Per-user preferences are in Settings > Notifications.

The Operator is reached at /operator and toggled from Settings > General. It is not an item in the Company group.

Billing and the wallet

Your organization has one wallet, at Wallets in the System group of the rail — not under Billing. It holds the token balance agents spend, and supports auto-refill: set an amount and a threshold and Horizon tops it up when the balance falls below it. Overdraft is rejected rather than allowed, so an empty wallet stops agent work.

Billing is a separate System item covering your subscription — tier, status, and the Stripe customer portal for payment details.

To control spend per team, give a department a budget: a monthly amount, an alert threshold (80% by default), alert recipients, and an overage policy.

API access

1. Create an API key

   Go to Settings > API Keys and select Create API Key. Give it a name, then set:

   • Permissions — a matrix of what the key may do, per module feature, rather than a single read/write/admin level.
   • Board scope — all boards, or a named subset.

   Keys are prefixed hzn_.

   Caution

   The secret is shown once, at creation. Copy it then — you cannot see it again. If you lose it, revoke the key and create another. Never commit a key to version control.

2. Call the API

   The API is at https://api.horizonplatform.ai/api/v2, and keys authenticate with a bearer token. To check a key works:

   curl https://api.horizonplatform.ai/api/v2/agent/boards \
     -H "Authorization: Bearer hzn_your_key_here"

   A 401 means the key is wrong or revoked; a 403 means the key is valid but its permissions or board scope do not cover what you asked for.

3. Schedule recurring agent runs

   Horizon runs agents on a cron schedule with IANA timezone support, so “every weekday at 08:00 America/Denver” means what it says through daylight-saving changes.

4. Trigger an agent from another system

   A webhook in Horizon is an inbound trigger: you create one against an agent, Horizon issues a token, and an external system calls that URL to start a conversation. A webhook carries a name, description, an enabled flag, an optional IP allowlist, and a default payload.

   Horizon does not send outbound event notifications, so there is nothing to subscribe to and no signing secret to verify.

Configuration checklist

• Company profile completed, including niche, ideal customer profile and targets
• Goals defined with measurables and dates
• Organization name and description set
• Roles reviewed against the seven built-ins
• Team invited and assigned roles
• Guest access configured, if you use it
• Departments created, with agents and connections attached
• Every connection showing Active
• Apps deployed from the Store
• Agent instructions customized
• Navigator set up and Altitude Checks arriving
• Wallet funded, auto-refill set
• Department budgets set where you need spend control
• API keys created with the permissions and board scope each caller needs
• Scheduled runs configured
• Inbound webhooks created for systems that need to trigger an agent

Next steps

• Platform guide — every feature of the dashboard.
• Building custom agents
• API reference