Developer
Create account API keys and manage request-validation secrets for custom integrations.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Create account API keys and manage request-validation secrets for custom integrations.
Concepts covered
Step breakdown
- Open DeveloperStart in the Developer section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
Developer is the API access surface for the account. The real screen shows API Keys, Account API Keys, Create API Key, copy/regenerate/delete controls, and a Secret key for request validation section.
This page exists for custom integrations, external systems, and implementation work that needs controlled API access.
What each control changes
Create API Key creates an account-level key. Copy moves the key into an implementation environment. Regenerate rotates access. Delete removes the key. The request-validation secret is used by receiving systems to validate signed requests from the account.
Treat keys as production credentials. Name keys by purpose, rotate them if exposure is suspected, and delete unused keys before they become hidden access paths.
Operational outcome
Developer settings make custom integration work inspectable. Teams can connect Frontline to their stack while keeping API access explicit, named, and revocable.
Operational playbook
Use Developer as part of the Frontline Admin Developer operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Developer control?
Create account API keys and manage request-validation secrets for custom integrations.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.