Examples

1. Self-serve signup (sole proprietor: corporate + manager)

Anyone can sign up without an administrator. The product creates a linked workspace: your company and your manager account are created together under one shared identity, and you start with a default team. On the free plan you can have up to two teammates in total, with at most two on a team. An administrator can later upgrade the same workspace to Pro: three teams, up to ten people per team, and up to thirty distinct teammates across the whole workspace.

• After you submit signup, you confirm your email using the link we send. That activates your manager account and starts a session so you can use the dashboard as the owner of that company.
• Sign-in uses one email-and-password form: we first look for a confirmed manager with that email; if none, we try a corporate user. You always land in the right role for the account that matched.
• From account settings you can change the password for whichever type of account you are currently signed in as—manager or corporate user.

2. Corporate and manager registration (admin path)

Separately from self-serve signup, an administrator can register a company and then invite its managers by email. Those managers complete registration through their invitation link.

Creating a corporate (admin)

Under Dashboard → Admin → Corporates → Add Corporate, the admin enters the company name and contact details. Only an admin can submit this form; the values are validated; a new company record is stored and the admin is sent back to the corporate list.

Inviting a manager (admin)

From the corporate list, the admin chooses Add Managerand enters the future manager's email. The system checks that the company exists, that this email is not already a manager for that company, then creates a pending manager with a temporary password and a short-lived invitation link. An email goes out with a link to finish registration. Invitations that are never completed can be removed after they expire (for example by an automated cleanup job).

Manager completes registration

The manager opens the invitation, sees their email and company prefilled, sets their own password, and submits. They receive a second email to confirm their address; confirming verifies the account, opens a manager session scoped to that company, and takes them to the corporate dashboard.

3. Corporate user registration and team assignment

Corporate users are team members. A manager invites them and chooses which team they join at invitation time. The same person can belong to more than one team once they exist in the company.

Manager invites a corp-user

From Dashboard → Corporate → Corp Users → Add Corp User, the manager must already have at least one team. They enter the invitee's email and pick a team. The flow checks that the manager is signed in, the team belongs to their company, the email is not already used for another user in that company, and that plan limits on team size and total headcount are respected. A pending user is created, linked to the chosen team immediately, and notified by email. After they finish registration and confirm email, they sign in and land on the issues area.

4. Manager: updating teams and users

Under Dashboard → Corporate, managers use the Teams and Corp Users areas to shape structure: create and rename teams, remove teams, and move people between teams.

Teams: create, update, delete

Creating a team requires a signed-in manager; the name is validated, and the team is tied to that manager and company. Updating or deleting a team is allowed only for the manager who owns that team (or an administrator). Deleting a team removes it and clears memberships for that team.

Adding a user to a team

On a team's edit screen, the manager sees current members and can add anyone from the same company who is not already on that team, or remove someone from the team. The same checks apply as for invitations: the team must be yours, the person must belong to your company, and plan limits on members per team still apply when adding.

5. Issues: create, assign, filter, update

Issues usually live in a company context: they may reference a team (some rows have no team). The creator is recorded as either a corporate user or a manager. Managers can also create personal issues tied to their own account while still staying under their company for access control. Assignments can point to another corporate user or a manager in the same company.

Creating an issue

Title, description, status, and priority are validated. New issues cannot be created already closed—closing is a separate step from the issue detail view when your role allows it. A corporate user must pick a team they belong to and is recorded as the creator. A manager picks a team they manage and is recorded as the creator.

Updating an issue

A corporate user may edit if they created the issue, are assigned to it, or belong to the issue's team. A manager may edit any issue that belongs to their company, including personal manager issues, using the same notion of company ownership as the detail page. Edits cover title, description, status, and priority—not reassignment here. If an issue is closed, only a manager may change its status again (for example to reopen); corporate users cannot reopen a closed issue through a status change.

Assigning an issue to a user or manager

Assignment only applies when the issue is on a team. The person changing assignment must either own that team as a manager or already be allowed to edit the issue as a corporate user. You can clear the assignee or set it to another corporate user or manager in the same company; the system checks that the chosen assignee actually exists in that company.

Filtering issues

For corporate users, tabs highlight issues they created or that are assigned to them, optionally narrowed to one team on the client. For managers, the view can span all teams in the company, include issues with no team where policy allows, or focus on a specific teammate's assignments. Search filters titles on the data already loaded. Status filters apply the same way; by default, "all" hides closed items for everyone. Viewing and filtering strictly to closed issues is reserved for managers.

6. Admin: all issues (paginated)

Dashboard → Admin → All Issues shows every issue in the product, ordered in pages with a fixed page size. Administrators can move between pages using the controls on that screen. Only admin accounts can open this view.