Welcome to Atono! As the person who created your company's workspace, you're automatically the Workspace Owner, which means you have the highest level of access in the system, including billing and plan management. This guide walks you through everything you need to do to get your workspace ready for your team.

If you'd prefer to share setup responsibilities, you can assign additional Administrators before you get started. Administrators have almost all the same permissions as the Workspace owner, with the exception of billing.

This guide is organized around the decisions you'll make as you set things up, not just a list of features. The biggest one is whether you're migrating from another tool or starting from scratch — we'll take you through both.

---

1. Create your workspace

If you've landed here, you've likely already completed this step, but if not you can find instructions here.

A couple of things worth noting:

• Your workspace name is also your workspace URL — and both are permanent. For example, if you named your workspace Acme, your team will access it at acme.atono.io. Take a moment to make sure you're happy with it before moving on.
• Atono uses passwordless login. There's no password to set or manage. When anyone (including you) logs in, Atono sends a magic link to their email. If you plan to use SSO, you'll set that up later in this guide.

---

2. Importing your data (optional)

If you're not importing data, skip ahead to Set up your teams.

Atono currently supports imports from Jira and Linear. If your team is using either tool, importing your data should be your first step. When you run an import, Atono brings in your existing team structure and populates it with your stories, bugs, assignments, and history automatically, so there's no need to set up teams manually beforehand.

📘

Teams created through an import are set up as Kanban teams by default. If some of your teams work in Scrum, you can convert them after the import is complete. We'll cover that in Set up your teams.

If you know ahead of time which teams should be private, you can create those in Atono before running the import — as long as the names match, the importer will assign issues to the existing private teams rather than creating new public ones. You can also change a team's access type at any time after the import. See Public vs. private teams.

---

3. Set up your teams

Teams are the core organizational unit in Atono, where work gets planned, tracked, and delivered. Before you start creating teams, it's worth thinking through how your organization actually works. A few decisions you make here will shape how your team experiences Atono from day one.

If you imported your data from Jira or Linear, your teams have already been created. You can skip ahead to [Convert imported teams to Scrum] and [Customize your workflows].

Kanban or Scrum?

When you create a team in Atono, the first decision is which methodology it uses. This determines how work is organized and which features are available to the team.

You can switch a team's workflow type at any time. Just be aware that switching to Kanban will delete any existing sprints, and switching to Scrum will move in-progress items back to To do, so there's a bit of cleanup involved either way.

Public or private?

The other decision when creating a team is whether it's public or private.

Both settings can be changed at any time from the team's settings.

Create a team

See Create a team.

Convert imported teams to Scrum

If you imported your data and some of your teams run Scrum, you can convert them from the team's settings. See Edit a team's details for instructions.

Customize your team workflows

Each team in Atono has its own workflow, with its own set of steps that stories and bugs move through from start to finish (for example, To do, Development, Review, and Done). Atono provides a default set of steps, but you can rename them, reorder them, change their colors, or add new ones to match how your team actually talks about their work.

Even though each team can have its own step names, Atono organizes all steps into four categories behind the scenes: To do, In progress, Done, and Won't do. This is what makes it possible to compare performance across teams even when their workflows look different on the surface.

Workflow customization can be done at any time by a workspace Administrator or team admin, so it doesn't have to be part of your initial setup. That said, getting it in place before you invite your team means everyone joins a workspace that already speaks their language.

For more details, see Customize workflows.

📘

Delegating team setup

If someone else on your team will be handling team setup, make sure they have the right permissions before handing off. You'll want to give them a Workspace Administrator role or make them a team Admin for the relevant teams. See Roles and permissions for more details.

---

4. Invite your team

With your teams set up, you're ready to bring people in. You can invite users from the Home page or the Manage users page — just enter their email addresses and Atono will send them an invitation.

A few things to keep in mind:

• The number of users you can invite depends on your plan. Both active users and pending invitations count toward your seat total, so if you need to make room, you can cancel pending invitations or deactivate users you no longer need.
• Invitations expire after 7 days. If someone doesn't accept in time, you can resend the invitation from the Manage users page.
• If you imported from Jira or Linear, some users may have already been added to your workspace as inactive users. You can invite them from the Manage users page once you have available seats.

Assigning roles

By default, everyone joins as a Standard User. Depending on how your organization is structured, you may want to assign different roles to some users before or after they join. See Roles and permissions for a full breakdown of what each role can do.

For more details on inviting and managing users, see Manage users.

---

5. Connect your integrations

Atono integrates with Slack and GitHub to keep communication and development connected to your team's work. Both integrations need to be enabled by a workspace Administrator or Owner before anyone else can use them.

---

6. Configure workspace settings

With your teams set up and your integrations connected, there are a few workspace-level settings worth reviewing. These are all Administrator-only, and none of them are urgent, but getting them in place early can save you work later.

---

7. What's next

Your workspace is set up and your team is ready to go! Here are a few things to point them to as they get started.