Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

1. Back-End Management

Manage your portal

1 Introduction

1.1 Function introduction

In the management background of the workspace, you can view the workspace overview, set basic information, find all applications, configure the navigation menu, manage permissions or browse bill details.

1.2 Application scenarios

You need to view an overview of the functional quota data of your own workspace, or configure the navigation menu, etc., to facilitate monitoring of usage or overall configuration of the workspace.

2 Setup steps

2.1 Function entrance

After entering the workspace, click "More" on the left navigation bar to enter the "Management Backstage"

2.2 Function setting steps

2.2.1 Workspace Overview

In the workspace overview, you can view an overview of the workspace quota data, invite colleagues to join for additional trial days, or view version features

Workspace quota data overview: Displays the available and used quotas for the current month. Click "Usage Details" to browse the usage details of each quota in detail, and click "Purchase Quota" to add new quotas to the workspace purchase. Among them, the introduction to the number of automation triggers and the calculation method of the number of triggers can be found below.

2.2.2 Basic information

In Basic Information, you can modify the basic information of the workspace, configure attachment permissions, configure global watermarks, transfer to the super administrator or set whether to hide the logo.

External links - public link permissions/attachment permissions (this function is only for unpaid customers, there is no limit for paid customers)

Allow public links: Can the permission scope of forms, reports, views, and portal functions be allowed to be visible or fillable to everyone?

After checking , when configuring the visibility range of forms, reports, views, and portal functions, you can choose the option of "Visible to everyone" or "Fillable to everyone"

When unchecked, the option "Visible to everyone" or "Fillable to everyone" is not allowed.

Allow the use of the "Attachment Upload" field: Can the permission to use the "Attachment Upload" field be allowed?

After checking , you can add the "Attachment Upload" field when using "Form Design"

When unchecked, the "Attachment Upload" field cannot be added.

The above functions can only be configured by the super administrator. If the system administrator needs it, he can contact the super administrator to assist in activating

2.2.3 All applications

Applications or portals in the workspace can be queried, deleted, or the visible scope and application packages to which they belong can be changed.

2.2.4 Navigation menu

You can add applications, portals, and application packages as menu items to the main navigation , and set the corresponding visibility range for each menu item.

2.2.5 Permission management

analysis administrator permissions to people in this workspace .

2.2.6 Workspace log

System optimization: Logs can help developers analyze system performance issues, optimizing and improving system stability and user experience.
Security assurance: Logs can help monitor potential security vulnerabilities and abnormal behaviors. By monitoring logs and analysis, business risks can be reduced.
Traceability and error checking: it can help developers quickly locate problems when they occur and make error corrections.

2.2.7 Bill details

You can view billing records after version/quota purchase.

After the configuration is completed, it must be published uniformly to take effect on all members of the workspace. Click the "Publish" button. Depending on the visible range, different members will see different navigation menus in the left navigation bar . The first page that members can view will be displayed as the home page of the member navigation bar by default.

2.3.4 Edit menu items

Click the "Basic Information" button on the right to edit the icon, name, visible range and content source

2.3.5 Delete menu item

Click the "Delete" button on the right to delete the corresponding menu item. Deleted items cannot be recovered.

3. Member use

3.1 View navigation menu

Depending on the configured visibility range, different members will see different navigation menus in the left navigation bar. When there are a large number of menus, you can scroll through them. Click the "triangle" button below the menu to expand the list and view all navigation menu items

3.2 View configuration content

Click a menu item to jump to the specified page of its configuration

Number of automation triggers

1. Function introduction

The number of automation triggers refers to the sum of the trigger times of Q-Robot within the process, Q-Robot outside the process, WebHook and process timeout.

2. Function setting steps

2.1 Function entrance

Enter the "Administrative Backend" of the workspace and click "Workspace Overview" to see the available and used quantity of automation triggers in the current month in the workspace quota data overview.

The "total amount of data submission" of proprietary light flow is unlimited and can be used freely.

3. FAQs

3.1 How to calculate the number of automation triggers?

Function	Trigger counting method
In-process Q-Robot	Each time a piece of data passes through the Q-Robot node in the process (adding data, updating data, sending text messages, sending emails), it will be counted once.
Webhook	Each time a piece of data passes through the Webhook node, it is counted once.

Example 1 : Suppose there are three branches in the process, and each branch has an in-process Q-Robot/Webhook node. If a piece of data meets two of the branch conditions, the number of triggers is counted as 2.

Function	Trigger counting method
Out-of-process Q-Robot (Q-Robot that needs to be configured in the extended settings)	The "first trigger time" is "when data is added" or "when data is updated", and each piece of data that meets the conditions is counted once.
	The "first trigger time" is "when Q-Robot fails to execute", and each piece of data that meets the conditions is counted once.
	The "first trigger time" is "according to the time field in the form", and each piece of data that meets the conditions is counted once.
	The "First Trigger Time" is "Customized", and each piece of data that meets the conditions is counted once.
	The "First Trigger Time" is "Based on the time field in the form" or "Customized", and when the application is republished, each piece of data that meets the conditions will be counted once.
	The "first trigger time" is "when the custom button is clicked to trigger". Depending on the trigger action, each piece of data that meets the conditions is counted once.
	The "first trigger time" is "according to the time field in the form", and by adding/updating data (not batch modification), if the number of new data within the filtering range is added, each additional piece of data that meets the criteria will be counted once.
	When the trigger action is "Add Data", each piece of data that meets the conditions will be counted once.
	When the trigger action is "Send Reminder", it will not be counted.

Example 2: If the "First Trigger Time" of a piece of data is set to "Customized" at 8 am tomorrow morning, and the modified time tonight is 9 am tomorrow morning, and the application is re-published, the number of triggers as of tonight will be counted as 2, at 9 am tomorrow morning Counted as 3 times after triggering

Example 3: A piece of data triggers Q-Robot outside the process through a custom button . When the trigger action is to add data, the number of triggers is counted as 1 time; when the trigger action is to send a reminder, the number of triggers is not counted.

Example 4: If 2 pieces of data in the original filtering range meet the triggering conditions, the number of triggers will be counted as 4. At this time, if 1 piece of data that meets the conditions is added, the number of triggers will be counted as 6 times.

Example 5: If a piece of data passes through the node that adds data, the number of triggers is counted as 1; if there is a piece of data that passes through the node that sends reminders, the number of triggers is not counted.

Function	Trigger counting method
Process timeout	Every time a piece of data passes a timeout, the time node is triggered and counted once.
	A piece of data is automatically submitted to the node after a timeout and counts once.
	Each time a piece of data passes through the timeout warning node, it is counted once.

Example 6: If a piece of data is set with a timeout trigger time, it will be counted once after triggering; if a piece of data is set with a timeout trigger time and automatically submitted after timeout, then a total of 2 times will be counted after submission.

3.2 Why is it that when the "First Trigger Time" is "Based on the time field in the form" or "Customized", after re-releasing the application, each piece of data that meets the conditions will be counted once?

the data of "based on time field in form" or "custom" is already in the queue waiting to be triggered when it is published, a new queue will be added every time the application is republished. Therefore, in these two cases, a piece of data will be counted once when it is published, and it will also be counted once after the action is triggered.

Transfer to super administrator

1 Introduction

1.1 Function introduction

Support workspace creators to transfer super administrator rights independently

1.2 Usage scenarios

Applicable to situations where the original super administrator has resigned or is unable to assume workspace management. You can use the transfer function to transfer the super administrator to another person.

1.3 Display effect

2. Setup steps

2.1 Function entrance

Enter the "Admin Backstage", click "Basic Information", and scroll down to find "Transfer to Super Administrator"

2.2 Select to be transferred to super administrator

Click the Transfer Super Administrator button, select the system administrator in the workspace as the transfer target, and click Confirm.

The transferee must be the system administrator.

The person being transferred cannot be a super administrator of other workspaces.

Click Send Verification Code. The verification code will be sent to the current super-managed mobile phone number for verification. Once the verification is passed, the transfer can be completed.

2.3 Reminder after transfer

After the transfer is successful, the original supervisor will receive a reminder of the successful transfer. At this time, the original super administrator no longer has super administrator privileges, but other privileges and identities are not affected.

After the transfer is successful, the new super administrator will receive an on-site reminder of the permission change. At this time, the new super administrator has super administrator rights.

3. Precautions

Transferring to a super administrator requires personal authentication, and security information must be supplemented before the transfer operation can be performed.
When uninstalling and reinstalling the Anffy application on a third-party platform , the super administrator of the workspace will be re-determined as the administrator of the Anffy application.
one person can be transferred to be the next super administrator.

All applications

1 Introduction

1.1 Function introduction

Applications and portals in the workspace can be managed uniformly. Administrators can quickly find their own applications and portals in "All Applications", view and modify their basic information, and delete applications and portals.

1.2 Usage scenarios

Suitable for scenarios where quick operations on applications or portals in the workspace are required. For example, after product testing is completed, the corresponding test application package can be quickly deleted in "All Applications"

1.3 Effect display

As shown in the figure below, quickly delete the expired "2020 Test Application Package" in "All Applications" to improve work efficiency.

2. Setup steps

2.1 Function entrance

Click the "More" button on the homepage to enter the "Management Backstage" interface, select "All Apps", and you can make related settings for "All Apps"

2.2 Function setting steps

2.2.1 Search application/portal name

You can search the portal or application through the search box, supporting keyword search and pinyin search.

Keyword search : Search by entering keywords in the application/portal name. For example, searching for "Zhang" will search for ""Zhang Test Application", "Zhang Work Board", etc.
Pinyin search : Search by entering the name of the application/portal. For example, searching for " HR " will search for: "[HR] Recruitment Overview", "[HR] Employee growth management", "[HR Supervisor] Recruitment Overview", etc.

2.2.2 View basic information about applications or portals

You can view the "visible scope", "application package", "creator", "creation time", "latest updated person", "latest updated time", "latest publisher" and "latest publisher" of the application or portal on all application interfaces. Last published time"

2.2.3 Accessing applications or portals

Click on the name of the application or portal to jump to the corresponding application or portal

2.2.4 Edit basic information of application or portal

You can edit basic information such as the "name", "visible scope" and "application package to which it belongs" of the application or portal. Click the "Basic Information" icon to enter the editing interface

2.2.5 Delete an application or portal

Apps or portals can be deleted. Click the "Delete" icon to perform the deletion operation

3. Precautions

When accessing an application or portal, when the application or portal is added in multiple application packages, it will jump to the application package with the earliest addition time.

Application recycle bin

1 Introduction

1.1 Function introduction

You can view basic information such as the name of the deleted application, the application package it belongs to, the person who deleted it, and the time of deletion. You can also restore the deleted application or delete it completely.

1.2 Usage scenarios

Suitable for scenarios where you need to recover accidentally deleted apps or completely delete apps. For example, after a company's business line is abandoned, the applications of this business line can be completely deleted.

1.3 Effect display

As shown in the figure below, restore the deleted "Information Entry" application in the "Application Recycle Bin"

2. Setup steps

2.1 Function entrance

Click the "More" button on the homepage to enter the "Management Backstage" interface, select "All Apps", and click "Application Recycle Bin" to make relevant

2.2 Function setting steps

2.2.1 Search application name

Applications can be searched through the search box

As shown in the figure, enter the keyword "Car" and search to get the "Car_info" application

2.2.2 View operation records

You can view the administrator's operation records in the "Application Recycle Bin", click "View Operation Records" to view

As shown in the figure, in the "Operation Record", check the deletion person and deletion time and other information when performing the "App Delete" and "App Restore" operations.

2.2.3 View basic information of deleted applications

You can view basic information such as the name of the deleted application, the application package it belongs to, the person who deleted it, and the time of deletion in the "App Recycle Bin"

2.2.4 Restore application

Deleted applications can be restored. Click the recovery icon and click the "Confirm" button to complete the function settings.

As shown in the figure, restore the deleted "Product Information" application

2.2.5 Completely delete the application

Deleted apps can be completely removed. Click the "Delete" icon and click the "Confirm" button to complete the function settings.

As shown in the picture, completely delete the "Product Information" application

3. Precautions

Deleted applications will be kept in the "Application Recycle Bin" for 60 days, and will be automatically and completely deleted after expiration.
After the app is completely deleted, the app and data cannot be recovered, so please proceed with caution.

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.