Setting up your organization

For: an Owner, at initial setup. Takes about 10 minutes.

What this does

Before Stacktic can run offboarding or organize your tools sensibly, it needs a little structure from you:

a department hierarchy with one root;
a few teammates with the right roles;
some basic branding for the tool registry your employees will use.

None of this is required to start browsing tools. But the department root is required before you can run your first offboarding.

Designate your org root

Every organization in Stacktic needs exactly one org root: a single top-level department that everything else sits underneath. Tools tagged to the root count as company-wide, rather than belonging to one team.

That matters because of how offboarding works. It walks a departing employee's department up the tree, collecting every tool along the way. The root is the floor everyone hits.

If this isn't done yet, you'll see a banner on /settings/departments prompting you to set it up. You have two options:

Use an existing top-level department. Pick the one that represents your whole company (often the one already named after it).
Create a new department. Stacktic suggests "Company" as the name, but you can call it anything.

Either way, any other top-level departments you already have get moved underneath the new root automatically. This is a one-time step. Once designated, the root can be renamed. But changing which department is the root requires contacting support.

Build out departments

Beyond the root, /settings/departments is where you shape the rest of your org chart. Add departments, and set each one's parent to build the tree.

This isn't just cosmetic. It's what offboarding uses to figure out which tools a departing employee's team relies on. It's also how you can tag a tool to a department instead of the whole company.

Invite teammates and set roles

/settings/members is where you invite the people who'll use Stacktic alongside you. Three roles exist:

Owner: can do everything, including managing settings and granting Owner to someone else.
Admin: can do everything except manage settings. That covers tools, access, signals, people, offboarding, and Switchboard. This is the default for a new invite.
User: can manage every tool, its access, and its signals, and can read people's profiles. A team can add offboarding or Switchboard without making them an Admin.

Only an Owner can invite another Owner. Invite people who help manage tools as a User. If they also need offboarding or Switchboard, use a team. See Roles and permissions for the full breakdown.

Brand the tool registry

Your employees find and request tools through the tool registry. It's the employee-facing page they sign in to with Google. /settings/registry lets you make it feel like yours:

Accent color: a hex color used as the registry's theme color. Buttons and other filled controls automatically switch their text between light and dark. That keeps the text readable against whatever color you pick.
Logo: upload a company mark. It appears in the registry header and as the fallback avatar background.
Intro message: an optional welcome note shown above the tool list. It's useful for pointing people at the tools everyone starts with, or at where to ask for help.

What you'll see

Once the org root is designated, the setup banner disappears from /settings/departments. The org-root badge appears on that department's row. Your registry branding takes effect right away for anyone signed in.