# Sign in as an organization


# Sign in as an organization

Voice Portal accounts belong to organizations. The first person to sign up creates the organization and becomes its administrator; everyone else joins by invitation. This page covers how to create an account, accept an invite, sign in, and how roles and projects decide what each person can do.

![The Voice Portal sign-in screen](/img/screenshots/portal/login.png)
*Sign in at portal.imatic.ai with your email or username, or create a new organization from the sign-up link.*

## Create an organization (sign up)

Signing up does two things at once: it creates a new organization and makes you its owner.

![The Voice Portal "Create Organization" sign-up screen](/img/screenshots/portal/signup.png)
*Sign up with your organization name, country, your name, email and a password.*

### Steps

1. Go to **/signup**.
2. Enter your **organization name** and **country**, then your **full name**, **email** and a **password**.
3. Select **Create Account**.

The Portal creates the organization and makes you the **organization admin**. From here you own billing, team members, compliance settings and every project in the organization.

:::tip

Only sign up if you are starting a brand-new organization. If your company already has a Voice Portal account, ask an admin to invite you instead — that keeps everyone in the same workspace.

:::

## Join by invitation (accept an invite)

When an organization admin or project manager invites you, you receive an invitation link containing a one-time token.

### Steps

1. Open the invitation link, which lands on **/accept-invite**.
2. Confirm your details and set a password.
3. Submit to join the organization with the role you were invited as.

You can invite and manage team members from [Workplace & team](./workplace-team).

## Sign in

1. Go to **/login**.
2. Enter your **email or username** and your password.
3. Sign in to reach the [Dashboard](./dashboard).

## Roles and permissions

Voice Portal has three roles. Each builds on the one below it.

| Role | Scope | What they can do |
| --- | --- | --- |
| **Organization admin** | Whole organization | Own billing, team members and compliance. Create and manage all projects, agents and campaigns. |
| **Project manager** | Assigned projects | Manage agents, campaigns and contacts within the projects they're assigned to. |
| **Member** | Assigned projects | View activity and perform limited actions; cannot manage billing or team. |

:::note

Day-to-day account ownership sits with the **organization admin**. Platform-level operations are handled by the imatic team.

:::

## Projects

A **project** is a group inside your organization that bundles related agents, campaigns and contacts. Projects are how larger teams keep work separate and tidy.

Each project carries:

- its own **timezone** and **locale**, so calling times and formatting match the audience;
- its own **user assignments**, so people only see the projects they work on.

This is the middle layer of the **Organization → Projects → Agents** structure described in the [overview](./introduction#the-three-tier-model). Create your projects before building agents so each agent, campaign and contact lands in the right place.

:::tip

Use one project per team, region or product line. Setting the project timezone correctly keeps outbound campaigns dialing at appropriate local hours.

:::

## Next steps

- [Open the Dashboard](./dashboard)
- [Create your first agent](./agents/create-agent)
- [Invite and manage your team](./workplace-team)
- [Set up billing and your wallet](./billing)