# Automation HQ (AHQ)

As Workato scales with your organization and the number of workspaces grows, the need for more granular control becomes critical. The automation HQ add-on allows admins to create independent workspaces and provides high level control and central management of all your managed workspaces. It also enables interoperability and information sharing between various independent organizational units.

Automation HQ setup

# Why is AHQ important?

With the HQ workspace, the enterprise console allows admins to create and manage independent workspaces for teams.

  • Governance.

    Central management across workspaces.

  • Empowerment.

    Empower business teams with dedicated workspaces to build and run automations.

  • Collaboration.

    Improve collaboration and sharing of reusable assets across teams and workspaces.

# Organization-wide settings

While workspaces operates independently, it is important to manage consolidated Audit log streaming, billing for total recipe and task usage, and approved custom connectors at the organization level.

  • Plan and billing period

    Managed workspaces automatically get the same set of features as HQ workspace depending on its subscription plan, however some add-ons can be enabled/disabled on individual workspace level.

  • Usage limits

    In Automation HQ workspaces share a pool of recipe and/or task limits. These limits can be distributed across all managed workspaces and updated ad-hoc.

  • Audit log streaming

    Automation HQ admins can set up org-wide Audit log streaming to make sure all logs are streamed in a single destination for all managed workspaces.

  • Custom connectors

    SDK connectors can be created in HQ workspace and shared with all managed workspaces.

# Managed Workspaces

A Workato workspace is your home base for building automations. While projects help to organize your automations by use-cases, creating separate workspaces help to organize recipes and other assets into meaningful groups for every department, level of business, or organization unit.

Each Workspace will have its own:

  • Lifecycle independence: they will each own a set of environments (Environment capability required)
  • Operational independence: Recipes, connections, API platform, Workbot, and other Workato tools
  • Team: Invite different set of collaborators and assign workspace-unique roles.

# What's next