Hierarchy in inabit

  • Users

    Overview


    This page outlines the Users concept in the Inabit system. A user represents an individual who has access to the platform and belongs to a specific organization. Each user has a unique identifier and associated profile information.

     

    Key functionalities:

    • Access and use assigned resources and data within the organization.
    • Perform specific actions based on assigned roles and permissions.
    • Update personal profile information.
    • Manage individual settings and preferences.

    Relationships:

    • A user belongs to one organization (N:1).
    • Users within the same organization may have different access levels and permissions.

       

    Additional Information:

    • You can find information on managing user accounts in the User Management API documentation: link.
    • For details on available roles and permissions, refer to the User Management API documentation: link.
  • Organizations

    Overview


    This page defines Organizations within the Inabit system. An organization represents a group of users that belong to the same account. It allows for granular access control and management within the platform.

     

    Key functionalities:

    • Create and manage users within the organization.
    • Assign specific roles and permissions to users.
    • Manage organization-specific settings and resources.
    • Track user activity and data within the organization.

    Relationships:

    • An organization belongs to one account (N:1).
    • An organization can have many users (1:N).
    • Users within an organization share access to specific resources and data based on their permissions.

    Additional Information:

    • You can find information on creating and managing organizations in the Organization Management API documentation: link.
    • For details on user roles and permissions, refer to the User Management section in the API reference.
  • Accounts

    Overview

    This page explains the concept of Accounts in the Inabit system. An account represents a single entity that uses the Inabit platform. This could be an individual, a company, or any other type of organization. Each account has its own unique identifier and is the top level of the Inabit hierarchy.

     

    Key functionalities:

    • Create and manage organizations within the account.
    • View and manage user access and permissions.
    • Access administrative functionalities for the account.
    • Billing and subscription information are all based on the account. (account-level)
     

    Relationships:

    • An account can have many organizations (1:N).
    • Organizations within an account share access to certain resources and settings.

     

    Additional Information:

    • You can find information on creating and managing accounts in the Account Management API documentation: link.
    • For details on available permissions and roles, refer to the User Management section of the API reference.
  • inabit Account Hierarchy

    This page clarifies the relationships between accounts, organizations, and users within the Inabit system.

     

    Key Terms:

    • Account: Represents a single entity that uses the Inabit system.
    • Organization: A group of users that belong to the same account. An account can have multiple organizations.
    • User: An individual who has access to the Inabit system and belongs to a specific organization. An organization can have multiple users. A user can be associated with multiple organizations as well.

    Relationships:

    • One account can have many organizations (1:N).
    • One organization belongs to one account (N:1).
    • One organization can have many users (1:N).
    • One user belongs to one organization (N:1).

    Example:

    • Inabit Corporation (Account)
      • Marketing Department (Organization)
        • User1 (Marketing Manager)
        • User2 (Social Media Specialist)
      • Sales Department (Organization)
        • User3 (Sales Representative)
        • User4 (Account Manager)