| Table of Contents | ||||
|---|---|---|---|---|
|
Note: These settings are limited to the Admin and Owner user roles. We recommend everyone else read through this section to understand how Allstacks processes your data, and how to follow-up if a tool or employee is not available at the team-level.
Adding Tools and Managing Resources
Adding and Removing Tools
The Allstacks journey starts with the services and tools your team uses. Connecting tools, and the items within them, allows Allstacks to provide powerful insights into your team’s patterns and history.
If you already have tools connected, you will see them listed similarly to the image above. Typically you only need one connection per tool/service. Note that any changes made on this page will impact any teams that use these tools.
You can add a new tool via the “Add Tools” located on the top-right of the page. It will open the following modal:
...
For additional questions about connecting tools, please reach out to your internal Allstacks lead or contact your Allstacks representative via the shared Slack channel or Microsoft Teams team.
Managing Resources within Tools
To limit what resources are enabled within a connection, click the gear icon with the “Configure Resources” label.
...
Settings to be aware of:
The toggle next to the enabled count will disable all children within a grouping. It needs to be enabled for any of the enabled children to be displayed in Allstacks.
Automatically enable new projects (repos, etc): When you create new projects or repositories in your source tools, Allstacks will download and process data from them automatically. You will typically want this on at the organization-level.
Note: Toggling individual projects/repositories off will remove them the views of any teams that might have been using them. Any item that is off will NOT be processed during the nightly pipeline run. To see data in a previously disabled item, check back on the next business day.
...