Managing your Organization

Get familiar with managing your team and securing user's authentication


StackOne allows adding multiple members inside your organization. You can invite all necessary users by specifying their email addresses and selecting the access role.

Table of contents:

  1. Manage team
  2. Authentication & Security logs
  3. Connection with Project settings & Accounts

Manage Team

If you have been assigned the "Org Admin" role, you will see an additional section, "Organization," in the left-side panel. For role "Basic", the section is hidden.

With "Org Admin" role, you can:

  • add a new member, as well as resend or cancel a previously sent invitation (via the invite tab)
  • Change a user's role
  • Disable/Enable any organization user
Manage Team demo

Authentication & Security logs

The Authentication menu enables the obligatory requirement of configuring Multi-factor authentication (MFA) for all accounts inside the Organization. MFA's main benefit is enhancing your organization's security by requiring your users to identify themselves with more than a username and password.

Once enabled, you will be prompted to configure MFA for your account. You can scan the QR code or enter the Authentication Secret manually inside your Auth app – Google Authenticator, Microsoft Authenticator, etc.
After binding the account, enter the Authenticator Code from the Auth app and click Confirm.



All organization users without multi-factor authentication already enabled will be required to do so the next time they log in the platform.

The Security Logs menu shows the user's post-login information – location, IP address, authentication result, and method. This menu monitors users' login activity to identify potential authentication issues and help meet your compliance & audit requirements.

Connection with Project settings & Accounts

Organization admins can also Create Projects. For each project created, you can decide who from your organization will have access and what privilege level is enough for a particular user.

For example, the same user can be an "Org Admin" but won't be able to change Project Settings if the Project role is "Viewer".

What’s Next