LogoLogo
TPI.devCommunityGithub
  • Overview
    • Introduction
      • Future Features
    • License & Disclaimer
    • APIM Architecture
      • Production Deployments and Capacity
      • Functions
      • Integration
    • Key Concepts
      • API Group
      • API Scope
      • API Client
      • End-to-End Workflow Combining API Group, API Scope, and API Client
        • Scenario: API Management for an E-commerce Platform
    • Support
    • Glossary
    • Scenarios
      • Financial Industry
        • Transforming Financial Services with digiRunner API Management
        • Redefining Financial Data Migration with digiRunner API Management Platform
      • Manufacturing Industry
        • Enabling Smart Manufacturing with Seamless API Integration and Automation via digiRunner
        • Streamlining Global Operations with API Management via digiRunner
      • Medical Industry
        • Enhancing Healthcare Data Integration and Security with digiRunner API Management
        • Revolutionizing Healthcare Interoperability with digiRunner’s Advanced API Framework
      • Insurance Industry
        • Modernizing Insurance Services with digiRunner API Management
        • Modernizing Insurance with digiRunner—Bridging Legacy Systems and Microservices
      • Government and Public Services
        • Empowering Open Government Services with digiRunner: A Mission for Integration and Transformation
        • Streamlining Public Sector Innovation via digiRunner: Driving Citizen-Centric Digital Transformation
  • Get Started
    • Installing digiRunner API Management
      • SMTP Configuration
    • Registering Your First APIs with digiRunner
    • Client Authorization and Calling APIs
    • Rate Limiting
    • Proxy Caching
    • Load Balancing
    • Sandbox Testing
    • VIP Gateway Priority Settings
    • JWE Certificate
  • Configuring IP Whitelisting via IP Binding
  • Most common use cases
    • Obtaining API Keys and Calling APIs
    • API IP Diversion
    • Viewing Real-time API Logs
    • Enabling APIs and No Auth in Batches with API Imported
    • Role-Based Access Management within a Hierarchical Structure
    • Simplified OIDC Login with Predefined Organizational Frameworks
    • Resetting User Password and Confirmation Email for Admin Console User
  • Guide
    • AC User Management
      • Users
      • My Profile
      • Roles
      • Role Mapping
      • Organization
      • Role & txID
      • Delegate AC User
      • AC OAuth 2.0 IdP
      • AC LDAP IdP
      • AC MLDAP IdP
      • AC API IdP
    • Development Mode
      • Function Management
      • Rtn Code Management
      • Embedded Function Management
    • Client Management
      • API Client
      • API Group
      • API Scope
      • Authentications
      • Security Level
      • GTW OAuth 2.0 IdP
      • GTW LDAP IdP
      • GTW API IdP
      • GTW JDBC IdP
      • Client Export/Import
    • API Management
      • API List
      • API Registry
      • API Test
      • API Modify Batch
    • Monitor & Alert
      • digiRunner Server
      • Alert Settings
    • Reports
      • API Calls
      • API RESP distribution
      • API Avg. RESP Time
      • API GTW traffic
      • Bad Attempt Report
    • Certificate Management
      • JWE Cert. List
      • JWE Cert. Management
      • TLS Cert. List
      • TLS Cert. Management
    • Application Forms
      • API Key
      • Applications
      • Approval Flow Settings
    • System Information
      • API Key Approval History
      • Scheduled Tasks
      • Recurring Tasks
      • Mail Log
    • System Configs
      • Setting
      • Items
      • Files
      • Customer Setting
      • Online Console
      • WebSocket Proxy Management
      • Static Webpage Reverse Proxy
      • RDB Connection
      • Mail Template Export/Import
  • API Integration Guide
    • Using Token for Authentication and Authorization
      • OpenID Connect (OIDC) Mode
      • Client Credentials Mode
      • Password Mode
    • Using X API Key for Authentication and Authorization
      • Applying for X API Key
      • Obtaining X API Key
      • Calling APIs Registered in digiRunner with X API Key
    • Using API Key for Authentication and Authorization
      • Applying for API Key
      • Obtaining API Key and Secret Key
      • Calculating the Signature and DGRK
      • Calling APIs Registered in digiRunner with API Key
    • Using HTTP Basic and OAuth for Authentication and Authorization
      • Calling APIs Registered in digiRunner with Basic Auth
      • Calling APIs Registered in digiRunner with No OAuth
    • Token Lifecycle Management Mechanism
      • Applying Refresh Token
      • Token Revocation
      • Token Introspection
    • JWS/JWE Integration
      • JWS Workflow
      • JWE Workflow
      • Exchanging Public Keys
      • Generating Certificate
      • Operating with JWS
      • Operating with JWE
Powered by GitBook
On this page
  • Create Organizations
  • Manage Organizations
  • Modify Parent Organization Name

Was this helpful?

Export as PDF
  1. Guide
  2. AC User Management

Organization

PreviousRole MappingNextRole & txID

Was this helpful?

Path: AC User Management > Organization

digiRunner adopts organizational hierarchy to manage API visual authorizations, and achieves comprehensive management of data permissions and function permissions based on the controls over role functions; the principle is that the upper-level personnel may only view the API of the lower-level personnel under their organization.

Take the figure below for example.

Personnel A belongs to the organization unit Department of Health, so personnel A can view the information of lower-level Physician and Administrative Assistant.

Personnel B belongs to the organization unit Department of IT > System Development Center, therefore, personnel B cannot see the information of the parallel organization Data Govemance Center, and cannot see the information of the upper-level organization Department of IT.

If external personnel has the need to use the system console, another organization for external personnel can also be created and accounts can be created.

Create Organizations

  1. Click Create to access the organization creation page.

  1. Fill in the data or make selections as instructed below. The fields marked with “*” are required.

  • Dept. name*: Name that can identify the organization.

  • Contacts name*: Person responsible for this organization.

  • Belonged dept.*: Select the upper-level organization.

  • Contacts telephone*: Phone number of the person responsible for this organization.

  • Dept. code: Code to help identify the organization; limited to alphanumeric characters, underscore (_) and hyphen (-).

  • Contacts email*: E-mail of the person responsible for this organization.

  1. When done adding the organization, click Add to save and exit.

Manage Organizations

In this section, you can find instructions on how to view, update and delete this organization list.

  1. Click on the desired organization to view the details of this organization, and click Update to access the update page.

  1. Modify the desired fields, and click Update to save and exit.

  1. To delete this organization, click Delete and a system prompt will pop up. Click Confirm to delete the organization.

Organizations cannot be deleted if:

  • The organization contains undeleted sub-organizations. The sub-organizations must be deleted first before the current organization can be deleted. Failure to do so will prevent the organization from being deleted, and a warning prompt will pop up.

  • The organization contains undeleted users. The users must be deleted or moved to another organization before the current organiztion can be deleted. Failure to do so will prevent the organization from being deleted, and a warning prompt will pop up.

  • The organization contains undeleted APIs. If a user within the organization has an API created, the user must be deleted or moved to another organization before the current organization can be deleted. Failure to do so will prevent the organization from being deleted, and a warning prompt will pop up.

Modify Parent Organization Name

  1. Click on the parent organization to be modified to view the details of this parent organization.

  1. Click Update to access the Update page.

  1. Modify the desired fields, and click Update to save and exit.

The can be used to expand / collapse the sub-organizations under them.

Click on the icon in the Belonged dept.* field to access the Organization chart page, select the department the organization belongs to, and click Confirm to proceed.