Skip to content

Request Joining Organization

Notes

  • This Use Case requires a modification of Sign-up Scenarios to add a user choice to provide the information for a new tenant or to provide the id of an existing tenant they want to join.
  • It is TBD when exactly to confirm the user by the system
    • Option 1: The user is only confirmed once there is an organization associated with it, either by creating one at sign up or associating with an existing one through this use case.
    • Option 2: The User is confirmed as soon as the profile is complete. In this case, the user would not have access to most of the functionality of the system.
    • Option 3: The User always creates their own “default organization” even if their intent is to simply join an existing one. Note that this is the model that GitHub follows by creating a “personal workspace” when creating a user.
  • The rejection message in case the company does not exist or the request is rejected by the tenant Administrator should be the same so that the system does not reveal information about what company names are registered with the system.

Steps

At Sign up time

  1. User Starts Sign up (local or SSO) process until they accept the T&C for use of Arda’s System.
  2. After Accepting T&C, the user provides its profile information and chooses whether to proceed with creating a new company or joining an existing one.
  3. If they choose to join an existing one, they must enter the unique name for the company in the system. The system will not provide assistance (e.g., autocomplete of company names) to fill in this field.
  4. The system will provide a confirmation of the request received and advise the user that they will receive an email to proceed. The user at this point is not confirmed by the system.
  5. If the company exists, the system will notify the administration user (Tenant Administrator) of the company about the request.
    - If the company does not exist, the system sends an e-mail to the user that their request could not be granted.
  6. The Tenant Administrator navigate to a page of pending requests and select the one for the requesting user.
  7. From this point, the use case proceeds as the Invite users use case after step 3 using the e-mail that the requesting user has provided.
    - If the Tenant Administrator rejects the request, the user will receive a message from the system that their request could not be granted.

Note: The rejection message in case the company does not exist or the request is rejected by the tenant Administrator should be the same so that the system does not reveal information about what company names are registered with the system.

After Sign-up time (second and further organizations)

  1. User navigates to their account profile page.
  2. Under a Section of “Organizations” that lists the organizations the user is associated with, the user selects the action to “request joining organization.
  3. The User enters the name of the organization they request to join.
  4. The Use case proceeds as the option At sign up time #4

At Sign-up Time Scenario

This scenario covers a new user requesting to join an organization during the sign-up process.

uml diagram

After Sign-up Time Scenario

This scenario covers an existing user requesting to join an organization.

uml diagram


Copyright: © Arda Systems 2025, All rights reserved

Comments