> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/tutorials/set-up-your-organization.md).

# Set up your organization

A 5-minute lesson that takes you from a fresh sign-in to a working organization with a workspace and an invited teammate.

{% hint style="info" %}
**By the end** you'll have created an organization, created your first workspace, and sent an invite to a teammate.
{% endhint %}

## Before you start

You only need to be signed in for the first time. The setup onboarding flow runs automatically when you have no organization yet.

## The setup

{% stepper %}
{% step %}
**Create your organization**

Sign in. DevAlly takes you to the **Set up your organization** screen.

Fill in:

* **Organization name**: your company's display name, e.g. `Acme Inc.`
* **Organization URL**: a unique identifier for your organization. The form prefills it from the name, but you can edit it. This becomes the URL where your team finds the platform: `app.devally.com/<your-org>`.

Select **Continue**. DevAlly creates the organization and moves you to the next step.

{% hint style="warning" %}
The URL is editable later in **Organization settings**, but changing it breaks any bookmarks your team has saved against the old one.
{% endhint %}
{% endstep %}

{% step %}
**Create your first workspace**

You see **Create your first workspace**.

Fill in:

* **Workspace name**: usually a team or area, e.g. `Growth team`.
* **Workspace ID**: three uppercase letters, e.g. `GRO`. DevAlly uses this prefix to identify accessibility issues, like `GRO-1204`. Pick something that will read well in issue references.

Select **Continue**. DevAlly creates the workspace and lands you on its overview.
{% endstep %}

{% step %}
**Invite your first teammate**

From your workspace, open the sidebar and go to **Settings → Organization**. Select **Invite member**.

Fill in:

* **Email addresses**: enter your teammate's email and press Enter. You can add more than one.
* **Role**: pick **Member** (default) or **Admin**.
* **Workspace access**: for Members, choose which workspaces they get and pick a role per workspace (Admin / Editor / Viewer). Admins automatically get every workspace.

Select **Send invite**. DevAlly emails the recipient a link.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**You're set up.** Your organization, workspace, and first invite are all in place.
{% endhint %}

## What's next?

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-user-plus">:user-plus:</i> <strong>Invite members</strong></td><td>Add more people, in bulk if needed.</td><td><a href="/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/how-to/invite-members.md">Invite members</a></td></tr><tr><td><i class="fa-shield-halved">:shield-halved:</i> <strong>Roles and permissions</strong></td><td>Pick the right role for each person.</td><td><a href="/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/reference/roles-and-permissions.md">Roles and permissions</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/tutorials/set-up-your-organization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.