Onboarding¶
Agentic Unit access is configured per user and per team. A user must be authenticated, assigned to a team, and given access to an agent before starting team-scoped work.
Request Access¶
The dedicated Service Desk onboarding and support queues are not yet live. Use the existing Agentic Unit platform team contact route and provide:
| Information | Description |
|---|---|
| Team name | The team that will use Agentic Unit. |
| Department | The responsible department or organizational unit. |
| Users | People who need web or CLI access. |
| Jira projects | Project keys that may trigger or be modified by agents. |
| GitHub organization and repositories | Repositories the team needs Agentic Unit to access. |
| Azure DevOps projects | Projects and repositories used by Azure DevOps automations, if applicable. |
| Required agents and workflows | Chat, Jira, PR review, Azure DevOps, pipeline, or scheduled use cases. |
Do not include passwords, personal access tokens, webhook tokens, private keys, or other secrets in the request.
User Sign-In And Team Membership¶
Authentication uses Cognito. Members of the aca-users group receive the
regular user role; members of aca-admins receive the administrator role.
On first sign-in, Agentic Unit creates the user's application record. An administrator must then assign that user to one or more Agentic Unit teams from Teams -> Members. There is no self-service team assignment. A newly registered user can therefore sign in successfully but initially see no teams or agents.
The web application is available only in environments where it has been
deployed. The Agentic Unit CLI currently provides built-in profiles for dev, int, and
cons; it does not yet provide a production profile.
Install And Link The GitHub App¶
For GitHub work, an organization owner installs the platform GitHub App and selects the repositories it may access. Grant access only to repositories where the team expects agents to work.
An Agentic Unit administrator then links the unclaimed GitHub App installation to the team. The team may be restricted to a subset of repositories from that installation. The selected team determines which installation and repositories an interactive job can use.
Configure branch protection before enabling a repository. Protect default and release branches from deletion and require pull requests and human approval before merging.
Configure Agents And Skills¶
Each team needs at least one agent. Agents can be created from a template and configured with a model, reasoning settings, system instructions, and attached skills. Team agents are visible to members of that team. Personal agents are visible only to their creator.
An integration works only when the selected agent has the required skill. For example, repository work needs the GitHub skill and Jira work needs a Jira skill.
Create Automation Credentials¶
Use the credential required by the target environment:
- Development Jira currently uses a legacy Jira webhook key because the v2 dispatch endpoint could not be allowlisted in Jira.
- Production Jira uses a scoped v2 trigger token.
- Azure DevOps and pipeline automations use scoped v2 trigger tokens.
Create credentials from the team's Integration credentials panel.
A trigger token fixes the owning team and channel. It can also be restricted to a Jira project, a default agent, or a list of allowed agents. The raw token is shown only once; store it in the automation system's secret storage. It remains valid until an administrator revokes it.
Legacy Jira webhook keys and the /v1/jira-events endpoint are deprecated in
the platform architecture, but they remain the required Development Jira setup
until the v2 endpoint is allowlisted. Production Jira uses the v2 dispatch
endpoint. Follow the environment-specific instructions in
Jira Automation.
Verify Onboarding¶
Before the first production-like task, confirm that:
- the user can sign in and see the expected team and agents;
- the team shows the correct GitHub App installation and repository scope;
- the selected agent has the required skills;
- the automation credential matches its environment and is stored securely;
- branch protection is active;
- a small test job reaches a terminal status and returns the expected report or branch result.
After onboarding, continue with Chat And CLI or one of the automation guides.