---
title: "Step 1: Workspace setup"
canonical: "https://support.appfire.com/space/FD/2832991013/Step%201%3A%20Workspace%20setup"
format: markdown
---
> Macro (aura-html)

The goal of this step is to: 

- Invite Admin user (or users).
- Create service accounts.

## Invite admin user

This is a **low-effort**, **real-time**, **recommended** configuration.

![Workspace setup, invite admin user tab.](media://e9199731-d724-4b64-be6d-011120955e3a)

Admins are responsible for, among other things, connecting integrations and ensuring that Flow can access your data. Because of this, they should understand your team's workflows, repositories, and tools.

While Flow automatically assigns an admin at the start, you can change this. If you aren't the right person to manage these configurations, please select at least one other person to be an admin. If they don't have access yet, send them a Flow invite and grant them admin permissions.

**Key takeaways for adding new admins**:

- Choose someone familiar with your team's technical tools.
- Ensure they have access to the platform.
- Assign admin permissions so they can manage data and integrations.

To invite an admin while on the Essential Setup page: 

1. Click the **Invite admin** button.
2. On the **Invite users to login** modal, enter the user's email address and assign their role or roles.

Visit the [Inviting and adding new users to Flow](https://appfire.atlassian.net/wiki/spaces/FD/pages/1801945504) and [Administrative permissions](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802142015) pages to learn more about inviting and granting permission to admin users.

Check the **I have invited admin users **box and click **Continue** to proceed to the *Service accounts and permissions* tab.

## Service accounts and permissions

This is a **low-effort**, **real-time**, **recommended** configuration.

![Workspace setup, create service account tab.](media://92d78834-a300-412b-b18a-d9712047a3ec)

Creating a service account lets you manage all organization repositories and API keys under a single, generic user. This prevents issues like permission changes or staffing turnover and ensures that personal repositories remain private and secure.

**Key benefits:**

- Keeps personal repositories private and separate.
- Prevents access loss due to staffing changes or individual permission updates.
- Manage all repositories and API keys through one unified integration.

Visit the [Service accounts in Flow](https://appfire.atlassian.net/wiki/spaces/FD/pages/1801977900) page to learn how to set up service accounts.

Check the **I have set up a dedicated service account and all necessary permissions are enabled **box and click **Continue** to proceed to [Step 2: Initial Configurations](https://appfire.atlassian.net/wiki/spaces/FDDRAFT/pages/2892333466).