AI GOUser Guide

Application Management and Access Control

This chapter is designed for enterprise administrators and developers. Custom Apps used by operational colleagues are managed in their lifecycle, assigned login URLs, and protected with Data Center table permissions through the global backend Dashboard.

Application Lifecycle Management

Under the "AI Applications" section of the left navigation bar, select "App Builder" to view all created Custom Apps. Here, administrators can perform the following operations:

  • Edit and Update Status: Modify input fields, system instruction prompts, or AI models used in the Custom App at any time. Click "Re-publish" to make updates live for colleagues.
  • Suspend and Take Offline: If a Custom App completes its task, administrators can click "Suspend". Users holding the dedicated login URL will no longer be able to log in.
  • Delete Application: Completely remove the application. Note that deleting a Custom App only removes its interface and dedicated login link, and does not delete historical records stored in the Data Center.

Management of Dedicated Login URLs

Each published Custom App generates a dedicated URL. Administrators configure the access type and distribute the link to users:

1. Generating Internal Login URLs

  • Target Audience: Internal employees or specific departments.
  • Management Operation: Select "Deploy as Internal App" in the App settings. The system generates an internal link based on your corporate domain.
  • Access Control: Limited to employees with corporate accounts (e.g., @yourcompany.com) who are added to the authorized user list.

2. Generating External Login URLs

  • Target Audience: External suppliers, partners, or customers.
  • Management Operation: Select "Deploy as External App". The system generates an independent external URL.
  • Access Control: Integrated with SMS code logins, temporary passwords, or supplier account systems.

Administrators copy these URLs from the Dashboard and distribute them to corresponding colleagues.

Data Center Table-Level Access Control

To protect core corporate data, AI GO enforces strict database table-level access controls. The ability of colleagues to read and write database tables through Custom Apps depends entirely on the administrator's settings here.

When creating or editing an App in the App Builder, you must configure the following settings in the core configuration panel:

1. Bind Authorized Tables (Table Mapping)

Specify which database tables in the Data Center the Custom App is authorized to access. For example:

  • Quotation App: Bind only the "Sales Order Table".
  • Leave Request App: Bind only the "HR Table".

2. Configure Table Permissions (CRUD Controls)

For each bound table, administrators configure fine-grained permissions:

  • Read-Only (R): The App can only read data and cannot modify it. For example, sales colleagues can read the "Product Specs and Price Table" in a product catalog App, but cannot modify prices.
  • Create & Write (C / W): Colleagues can add new records through the App. For example, the voucher entry App is authorized to write new records into the "Accounting Table".
  • Modify & Update (U): Colleagues can update existing database records. For example, delivery staff can change the shipping status field to "Shipped" in a delivery App.
  • Delete Permission (D): To prevent data loss, granting delete permissions on Data Center tables to general employees in Custom Apps is "strictly prohibited". All delete or invalidation operations should be designed as "modifying a status field to void", while physical deletion can only be performed by senior administrators in the global backend.

Through these three layers of protection (dedicated login URLs, bound authorized tables, and fine-grained CRUD controls), administrators ensure that while corporate operations are highly automated, data remains protected with vault-grade security.