Access and teams

Purpose

This guide explains how a person or agent signs in to Allye, selects the correct team, and understands why certain modules or actions may not be available. The active team is the primary context for working with boards, work items, documentation, and sprints.

Prerequisites

Have an Allye account or an invitation to an organization.
To administer users, teams, or access groups, have the corresponding management permissions.
To use MFA, have a compatible TOTP authenticator app.

Key concepts

Organization, user, and team

An organization is the workspace to which an account belongs. A user can participate in more than one team. Each team organizes its own work, configures its workflow, and may have different boards, documents, and members.

The account maintains an active team. It appears in the application's context selector and determines the default set of data shown in work areas.

Access groups and permissions

An access group brings together reusable permissions. Permissions are organized by module and action:

View: read or open a resource.
Create: add a resource.
Edit: change an existing resource.
Delete: remove a resource.
Import: bring data into Allye.
Export: download or extract data.
Manage: allow administrative actions and, where applicable, activity across teams.

The interface filters menus and buttons based on these permissions. Effective authorization is also enforced by the service: seeing a module does not mean that you can edit everything in it.

User states

In user administration, the observed states are active, invited, pending, inactive, and suspended. An invitation that has not been accepted is not equivalent to an active user.

Open Allye and select Sign in.
Enter an email address and a password with at least eight characters, including letters and numbers.
If the account requires verification, open the email you receive and complete confirmation before trying to sign in again.
If the organization requires MFA, follow the redirect to configure or verify the six-digit code.
Complete onboarding when prompted.
Confirm the active team before creating or changing data.

You can also start a session with Google or GitHub. The social sign-in flow returns to Allye to complete authentication; in integrations that request workspace access, review the selected team and approve or deny consent.

Recover your account

On the sign-in screen, use Forgot password? to request recovery. The link you receive lets you set a new password. An accepted invitation may ask you to create a password before your first access. If the email is not yet verified, the sign-in screen offers to resend the message, with a security interval between attempts.

Switch the active team

Open the team selector in the application shell.
Choose one of the teams you belong to.
Wait for navigation and data to refresh.
Check the board, sprint, and filters again before taking an action.

When you switch teams, Allye clears cached data related to the previous context, reloads queries, and reconnects real-time updates. This prevents items from two teams from being mixed on the same screen.

For agents

Before creating, moving, assigning, or completing any item:

Identify the organization and team the request is intended to change.
Confirm the agent session's active team.
Reread the context after switching teams.
Do not assume that read permission includes create, edit, or manage access.
If the request does not specify a team and more than one is available, ask for clarification instead of choosing silently.

Administer users

Open Team and the Users tab.
Use search and status or team filters to find a person.
Select Invite User to enter a name, email, initial team, and access group.
For an existing person, edit their name, team associations, or access group.
Resend the invitation when necessary.
Change the status to activate or deactivate access according to the organization's policy.
Use the confirmation before removing a person.

A person can belong to several teams. Removing a team is not the same as removing the user from the organization.

Administer teams and groups

Create and edit a team

In Team, open Teams.
Select New Team or edit an existing team.
Enter a name, description, and, when applicable, the prefix used in work item keys.
Save and confirm the team in the list.

Create an access group

Open the Access Groups tab.
Select New Group.
Enter a name, description, and whether the group should be the default.
Open the permissions matrix.
Mark permissions by module or action; use Select All, Clear All, or Reset carefully.
Save the permissions and associate the group with the required users.

The default group cannot be deleted. When another group is deleted, its users are moved to the default group, as described in the confirmation shown by the application.

MFA and access security

Enable personal MFA

Open Settings > Security.
Select Enable and confirm your password.
Scan the QR Code in an authenticator app or enter the manual key.
Enter the six-digit code shown by the app.
Confirm with Verify & Enable.

To disable it, enter your password again. If the organization requires MFA, the disable button is locked. An administrator with management permission can reset another person's MFA; that person must configure it again at the next sign-in when the requirement is active.

Current states and limitations

Current state: the frontend implements sign-in, social OAuth, email verification, password recovery, invitations, MFA, team switching, and consent flows. The final session, identity, and authorization rules depend on the account service connected to the workspace.

Protected navigation requires an authenticated session; public pages are limited to access and account recovery.
Menu visibility depends on the permissions loaded for the user and the current context.
Create, edit, and delete actions normally apply to the user's own team; manage permission is required for administrative operations across teams.
The status shown in the application may remain pending or invited while an invitation has not been completed.
The application contains a development mode for validating screens without real authentication. It is for development only and does not represent an end-user flow.

Next steps

Configure your profile and MFA in Settings.
Ask an administrator for the appropriate access group before starting work.
Read Work items to structure the team's work.
Configure the team's workflow before creating boards and sprints.