This article is part of a series of settings overview articles:










Aha! Develop | Team settings

Team-level settings affect individual teams in your Aha! Develop account. Open your team settings by navigating to Settings ⚙️ Team. You will need to be an owner to do this.

Team members

Every team has members — Aha! Develop users who collaborate with you on your work. Click this link to navigate to Settings ⚙️ Account Teams and see a list of your team's members. You will need to be an administrator with customizations permissions to do this.

Once there, you can Add team members, change individual members' permissions, or Remove members. Your changes will be saved automatically.



Next, let's work through the Configure settings. These settings affect a team's workflows, layouts, and record dates.


Record workflows define how your work progresses from creation to resolution. You can create custom workflows at the account level to define those pathways, along with custom statuses and transition buttons. Here at the team level, you get to select the workflow that your team will adopt for each record type.


  • You can assign the same workflow to multiple teams to help bring a consistent structure to how teams complete work in your Aha! Develop account.

  • Develop Advanced customers who have integrated with an Aha! Roadmaps account will see a parallel workflow in records that are shared between the two products. This allows development teams to have a workflow that matches their process, while product managers can still use a robust workflow that tracks the entire life cycle of a feature.

In this section, you can change the workflow for the four basic record types:

  • Releases

  • Epics (use the features workflow)

  • Features

  • Requirements (use the features workflow)

For each record type, the process to adjust a workflow is the same. Click Edit <record type> workflow to open the Change workflow modal. From here, you can change the workflow using the New workflow dropdown or map the statuses in your current workflow to new statuses using the New statuses dropdown. If you are adjusting the workflow for an epic, feature, or requirement, you can also map the record types from your current workflow to new types using the New types dropdown.

Click Update record statuses to save your changes. Any changes you save take effect immediately across every relevant record in your team.

Click the Custom statuses and workflows hyperlink next to each record type to navigate to Settings ⚙️ Account Statuses and workflows. From here, you can create, edit, or delete the workflows that you want to apply to your team. You will need to be an administrator with customization permissions to access this part of the settings.


Workflow syncing

Ambitious work gets completed one step at a time — feature by feature, requirement by requirement. You can already calculate an epic's or a feature's progress from its child records, but you might also want epic and feature statuses to update as contributing records progress through their workflow.

With these settings enabled, parent records' statuses will stay in sync with their child records' status categories. For example, once a feature moves to a status in the In progress category, the epic's status will change to the first status in its In progress category.

A few things to note about workflow syncing:

  • You can always manually change the status of any record.

  • The parent record's status will change once the first child record's status advances to a new status in the workflow.

  • The workflow sync follows your records through the workflow from Not started to Shipped or Will not do. It will not stay in sync if you move backwards in the workflow.

  • Workflow sync works with automation. However, if you use automation on the child record and the parent record has a fixed workflow, the statuses will not remain synced if syncing would cause the parent record to skip a step in its workflow.

  • If you have synced requirements and features, and features and epics, it is possible for a requirement's status change to update a feature's status, which then updates an epic.

To adjust these settings, use the appropriate dropdowns:

  • Epics: Choose whether an epic's status should automatically update when its features update.

  • Features: Choose whether a feature's status should automatically update when its requirements update.

Note: Epic and feature workflow syncing is enabled by default.


Custom layouts

The Custom layouts section helps you adjust the way that fields are laid out on records in your team.

Note: If you are a Develop Advanced customer integrated with an Aha! Roadmaps account, your Aha! Develop records have custom layouts that are unique to your account. This lets product managers and developers each have dedicated layouts showing only the information they need.

To create, edit, or delete a custom layout, you will need to be an administrator with customization permissions. Navigate to Settings ⚙️ Account Custom layouts for those adjustments. Owners can select which layouts get applied to the record types in their team.

You can change the custom layout for the following record types:

  • Team

  • Releases

  • Epics

  • Features

  • Requirements

For each record type, use the custom layout dropdown to select the layout you want the record to display in your current team. If you want to edit the custom layout you have selected (and you have the proper user permissions), hover over a record type and click Edit layout.



Your team will work best in Aha! Develop if they can work with language that they are used to. Instead of features, for example, you might prefer to work with user stories.

The Terminology setting section allows you to customize the names of Aha! Develop record types for your team.

  • Select Use default terminology if you would like to retain the default terminology for your team.

  • Select Customize terminology to customize each record type's terminology. You can also click this option to see the default terminology and adjust it as needed. Click Update terminology to save your changes.

The names you enter in this menu will be displayed everywhere in the team except the Settings pages.


Note templates

Note templates provide a ready-to-use format for the types of notes you create most. Aha! Develop offers seven example note templates to choose from when you create a note.

If you have specific details pertinent to your team that you want to include in a note template, create your own here.

Note: If you have integrated your Aha! Develop Advanced account with Aha! Roadmaps, you can share note templates between Aha! Roadmaps workspaces and Aha! Develop teams, and inherit them from Aha! Roadmaps workspace lines to drive consistency across teams and establish a standard approach for capturing information.

Click Add note template to create a template. Use the text editor to customize the note template to your needs — add tables, images, Aha! views, and more. You can also assign watchers, add to-dos, and change the title icon to an emoji to help your template stand out.

You can hover over created templates to View, Edit, or Delete them.


Automation (Advanced plan)

If you are a Develop Advanced customer, you can create automation rules in your team to streamline your work, drive consistency across your team's workflow, and free you up to focus on more complex projects.

Automation rules have two parts: triggers and actions. Each rule starts with a trigger. If the trigger occurs, then the actions you define will run automatically.

You can use automation rules to sync statuses across related record types (like epics and features), to notify Aha! users when certain fields are updated, or to create standardized to-dos when a record reaches a certain stage in its workflow.

Read this article for more information on automation rules.


Capacity planning

Use capacity planning to configure your effort estimation process — the amount of work it will take to complete a given record. Use these settings to configure defaults for your team.

  • Units for estimates: You can estimate work in either Story points or Time. The units you select here will be the default capacity planning units for all newly created records (though you can always change the units on a record individually).

    Note: If you are a Develop Advanced customer and have integrated your account with Aha! Roadmaps, we recommend that Aha! Develop and Aha! Roadmaps users use the same estimation units. This makes it much easier to collaborate on record estimation.

  • Remaining estimate: Choose what should happen if time logged does not match a record's estimate. Select Add as logged time if you want the remaining estimate to be logged as work done when you ship a record with an outstanding estimate. Select Ignore remaining time if you want the work log to ignore the remaining time estimate. Use this option to ensure that the logged time accurately reflects work that was done.

  • Estimate association: Two record types in your Aha! Develop account can have child records under them. Choose how you want to calculate effort estimations for these record types.

    • Features: Features can have child requirements.

      • If you associate estimates with requirements and create a feature with requirements, then the feature's capacity will be calculated from the sum of its requirements' estimates by default. You will not need to set the feature capacity manually in this case.

      • If you associate estimates with requirements but create a feature without any requirements, you will adjust capacity planning at the feature level.

    • Epics: Epics can have child features.

      • If you associate estimates with features and create an epic with child features, then the epic's capacity will calculate from the sum of its features' estimates by default. You will not need to set the epic capacity manually in this case.

      • If you associate estimates with features but create an epic without any features, you will adjust capacity planning at the epic level.

Click Update configuration to save your changes.


Aha! Ideas
Aha! Roadmaps
Aha! Develop