Full Configuration

Configure a Horizon organization end to end — company profile, goals, departments, connections, roles, billing, and API access. Takes 1–2 hours.

Full Configuration is the most thorough of Horizon’s guided onboarding flows: company profile, departments, platforms connected, and the Navigator set up. It takes 1–2 hours, and this page also covers the settings that live outside the flow.

Before you start

Complete the Quick Start first.

The guided flow

Horizon presents onboarding at /onboarding under Welcome to Horizon, where you pick a flow, among them 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, and the 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 context agents can work from: company name, industry, company size and founded year; your drive, horizon and code; core values; niche, ideal customer profile and geographic focus; and a 3-year picture and a 1-year plan. See Company Profile.

Goals

Company > Goals holds your goals and milestones. A goal has a title, description, type (Yearly, Quarterly or Stretch), an owner, a status and measurables, and can sit under a parent goal, so a yearly goal can carry quarterly ones. Milestones are the dated steps toward a goal. See Company Goals.

Organization settings

Settings opens on General: the organization name and description, the logo and primary color, and the Operator Chat switch, which is on by default. The other tabs cover users, guest access, API keys, notifications, labels, workspace approvals and finance. See Organization Settings.

Roles and users

1. Review the roles

   Horizon has seven built-in roles:

   Role	Stored as
   Owner	owner
   Admin	admin
   Department Lead	department_lead
   Member	member
   Billing Admin	billing_admin
   Controller	controller
   Accountant	accountant

   Every role except Owner can be chosen when you invite someone.

2. Invite people

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

3. Allow guests

   Settings > Guest Access controls whether board admins and editors can invite people from outside the organization to individual boards. See Boards.

Departments

Go to Workspace > Departments and select Create Department. A department has a name and a description, and can have an icon and a lead. To cap a department’s spend, open it and set a Monthly Budget (tokens).

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
• Slack
• Microsoft Teams
• Google (Gmail, Google Calendar, Google Drive)

A healthy connection shows active. When you disconnect a connection, Horizon lists the active agents that will lose access, with the skills that use it, and offers to Pause these agents.

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.

Company features

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

• Boards — task boards for people and agents. They are also the unit of scope for guest access and for API keys. See Boards.
• Navigator — the agent that watches the business against your goals.
• Altitude Checks — reviews the Navigator generates for a period when an owner or admin selects Generate Check Now: a scorecard, milestone review, issues, wins, recommended actions and an executive summary. See Altitude Checks.
• Notifications — your notification inbox. What notifies you, and where, is set in Settings > Notifications. See Notifications.

Operator, the chat window for talking to your agents, opens from the Ask AI button in the top bar and is switched on or off with Operator Chat in Settings > General. See Operator.

Billing and the wallet

Your organization has one wallet, at Wallets in the System group of the rail. It holds the token balance agents spend, and the page shows the balance and whether auto-refill is on. A charge the balance cannot cover is refused, so an empty wallet stops agent work.

Billing is a separate System item covering your subscription: your plan, its status, and Manage Subscription for payment details.

To control spend per team, give a department a monthly budget (see Departments).

API access

1. Create an API key

   You need the owner or admin role. Go to Settings > API Keys and select Create API Key. Give it a name, then set:

   • Module permissions — what the key may do, feature by feature (Read, Write, Delete, and Execute where a module offers it).
   • Board access — All boards, Only selected boards, or only the boards the key’s owner has been added to (shown as Owner’s boards in the key list), which the dialog recommends for agent and bot keys.

   Keys are prefixed hzn_. A key acts as the person who created it. See API Key Management.

   Caution

   The key is shown once, at creation. Copy it then — you cannot see it again. If you lose it, select Rotate on the key to get a new one; the old key stops working at once. 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:

   bashCopy

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

   A 401 means the key is wrong, revoked or expired; a 403 means the key is valid but its permissions do not cover what you asked for. A board outside the key’s board access is answered with a 404, as if it did not exist.

3. Schedule recurring agent runs

   Horizon runs agents on a cron schedule in the IANA timezone you choose, so “every weekday at 08:00 America/Denver” stays at 08:00 local time on both sides of a daylight-saving change. Around the change itself:

   • A time the clocks skip has no run that day, and a time the clocks repeat runs once.
   • The first run after you create a schedule, or change its timing or timezone, can still be an hour off if the clocks change before it. When clocks go back, that job runs twice that day, and each run is charged.

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, a description, default instructions for the agent, an optional IP allowlist, and an enabled switch. See Webhooks.

Configuration checklist

• Company profile completed, including your drive, niche and ideal customer profile
• Goals defined with measurables, and milestones added
• Organization name, description and logo set
• Roles reviewed against the seven built-ins
• Team invited and assigned roles
• Guest access set the way you want it
• Departments created, with monthly budgets where you need spend control
• Every connection showing active
• Apps deployed from the Store
• Agent instructions customized
• Navigator set up and a first Altitude Check generated
• Wallet funded
• 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