Requirements

Everything you need to get started. Setup takes about fifteen minutes.

Slack workspace

You need admin access to your Slack workspace to install the Awk app. Any Slack plan works — Free, Pro, Business+, or Enterprise Grid.

The app needs permission to:

• →Read and post messages in channels it's invited to
• →Receive direct messages
• →React to messages

GitHub organization

You need organization admin access to install the Awk GitHub App. The app requests permission to:

• →Read repository contents, issues, and pull requests
• →Create branches, commits, and pull requests
• →Post comments on pull requests and issues

Permissions are scoped per-repository — you choose which repos the agentic workers can access.

Jira Cloud (optional)

If you want agentic workers to work with Jira tickets, you'll need:

• →A Jira Cloud instance (Server and Data Center are not supported)
• →A Jira site admin to install the Awk Jira app (once)
• →Authorisation with Atlassian, done from the console's Integrations step

See Jira integration for assignment methods and workflow.

Google Workspace (for P.Chief)

If you want P.Chief to manage your email and calendar via Google:

• →A Google Workspace account (personal Gmail works too)
• →Permission to authorize OAuth access to Gmail and Google Calendar

See P.Chief setup for the step-by-step flow.

Microsoft 365 (for P.Chief)

If you prefer Microsoft:

• →A Microsoft 365 account
• →Permission to authorize OAuth access to Outlook and Calendar
• →Your organization's admin may need to approve the consent request

See P.Chief setup for the step-by-step flow.

No infrastructure required

AwkTeams is a fully hosted service. There is nothing to install, deploy, or maintain on your end. Your agentic workers run in isolated infrastructure managed by us.

All you need is a browser to access the console at console.awkteams.ai.