Expense List
Last updated
Last updated
Purpose: Controls access to specific expense details based on the user's relationship to the data.
Creator: The user who created the expense record.
Reimburser: The individual submitting the expense for reimbursement.
Reimburser's department: The department to which the reimburser belongs.
Expense beneficiary user: The user who directly benefited from the expense.
Expense beneficiary department: The department that benefited from the expense.
Defines the relationship between other parties and the associated user that determines their permission to access the data.
Myself: The associated user have access to data directly related themselves.
Superior: The user’s direct supervisor have access to the data.
All Superiors: All higher-ups in the organization hierarchy have access to the data.
Subordinates: Users reporting directly to the associated user have access to the data.
All Subordinates: All users lower in the organizational hierarchy have access to the data.
HOD (Head of Department): The department head has access to the data.
Same Department: Users from the same department have access to the data.
Same Role: Users with the same role have access to the data.
Purpose: Allows to configure the actions that the users are authorized to perform.
View: Provides read-only access to expense details.
Edit: Allows users to modify existing expense details.
Delete: Grants users the ability to remove expense details from the system permanently.
Purpose: Provides the ability to monitor and manage data at various organizational levels.
All Users: Permissions apply to all users.
Specific User: Permissions granted based on individuals.
Specific Role: Permissions granted based on role.
Specific Department: Permissions granted based on department.
Defines the scope of data a user can access based on their hierarchical position within the organization.
Myself: Access to data directly related to the user.
Superior: Access to data created by the user’s direct supervisor.
All Superiors: Access to data created by all higher-ups in the organization hierarchy.
Subordinates: Access to data created by the user's subordinate.
All Subordinates: Access to data created by the user’s direct subordinates and their subordinates (i.e., the entire reporting chain under the user).
HOD (Head of Department): Access to data created by the department head.
Same Department: Access to data created by all users within the same department
Same Role: Access to data created by users holding the same role, even if they are in different departments.
Purpose: Allows to configure the actions that the users are authorized to perform.
View: Provides read-only access to expense details.
Edit: Allows users to modify existing expense details.
Delete: Grants users the ability to remove expense details from the system permanently.
Purpose: Manages access to different features or functionalities within the Expense list.
All Users: Permissions apply to all users.
Specific User: Permissions granted based on individuals.
Specific Role: Permissions granted based on role.
Specific Department: Permissions granted based on department.
Purpose: Allows to configure the actions that the users are authorized to perform.
Add: Grants the ability to create new expense records.
Batch create: Enables the user to create multiple expense records simultaneously.
Batch delete: Allows the user to remove multiple expense records at once.
Import: Allows batch creation of records by uploading data from an Excel file.
Export: Allows the user to download data in Excel format from the OA system to local devices.
The log is defaulted to displayed as a timeline chart, with the time of occurrence shown on the left and the operation type and details displayed on the right.
In both view, the log can be filtered by operation type, by the creation time using the existing time filter, or by customizing the range with the "Time range" button.
The user can search log based on log content or operating target that match or are similar to the text entered in the search box.
Purpose: To provide clear overview of who is granted specific permissions and grouping the data by different dimensions.
Purpose: This dimension provides an overview of the specific types of permissions assigned (e.g., Add, Edit, Delete) and to whom they are granted.
Remark:
Permission Type: The type of action or permission granted (e.g., View, Edit, Delete, etc.).
Scope: Defines who the permission applies to (e.g., specific user, role, department, all users).
Data Filtering: This refers to any restrictions applied to the data a user can access based on specific criteria (e.g., only data related to their department, subordinates, or specific customers).
Purpose: Shows the individual users and the specific permissions they have, along with the extent to which they can access or modify data.
Remark:
User: The specific person (e.g., Axel, Matthew).
Data penetration: Indicates how deep the user's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Existing permissions: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the user can access based on filtering conditions (e.g., only customers from a specific region).
Purpose: Provides a role-based view of permissions, useful for managing large groups of users. It defines what permissions are granted to users based on their role in the organization.
Remark:
Role: Specifies the role (e.g., Account Manager, Support Engineer).
Data Penetration: Indicates how deep the role's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Existing permissions: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the role can access based on filtering conditions (e.g., only customers from a specific region).
Purpose: Provides a department-wide view of permissions, often used to grant broader access to users within a specific functional area (e.g., sales, support).
Remark:
Department: Specifies the department (e.g., Sales, Purchase).
Data Penetration: Indicates how deep the department's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Existing permissions: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the role can access based on filtering conditions (e.g., only customers from a specific region).
Purpose: Allows permissions to be controlled based on the relation of the user to specific data fields.
Remarks:
Associated field: Defines the user’s relationship to the data (e.g., Creator, Reimburser, Expense beneficiary).
Data Penetration: Indicates how deep the department's permissions reach (e.g., whether they can see only their own data, their subordinates' data, or a broader range).
Existing permissions: Lists the actions the user can perform (e.g., View, Edit).
Data Filtering: Specifies the data the role can access based on filtering conditions (e.g., only customers from a specific region).
