Administrator
1. Using Sanplex by Role
1.1. Administrator
1.1.1 Manage Departments
1.1.2 Manage Users
1.1.3 Manage Permissions
1.1.4 Configure Notifications
2. Introduction of Sanplex features
2.1. Core Management Framework
2.1.1 Program
2.1.2 Project
2.1.3 Product
2.1.4 Execution
2.1.5 Management Models
2.2. Dashboard
2.2.1 Getting Started with Tutorials
2.2.2 Quick Add
2.2.3 Notification Center
2.2.4 Effort Tracking
2.2.5 Dashboard - Project and Execution
2.2.6 Dashboard - My Work, Contribution, and Recents
2.2.7 Dashboard - Approval
2.2.8 Contacts
2.3. Program
2.3.1 Program List
2.3.2 Program Kanban
2.3.3 Create Program
2.3.4 Create Sub-Programs
2.3.5 Project Charter Management
2.4. Product
2.4.1 Create Product
2.4.2 Manage Modules
2.4.3 Multi-Branch and Multi-Platform Management
2.4.4 Manage Plans
2.4.5 Manage Stories
2.4.6 Story Reviews
2.4.7 Story Status and Phase
2.4.8 Create Releases
2.4.9 Track Progress
2.4.10 Epics and Multi-Level Stories
2.5. Project
2.5.1 Scrum Project
2.5.2. Waterfall Project
2.5.2.1 Manage Project Phases
2.5.2.2 Project Design
2.5.2.3 Project Matrix
2.5.2.4 Project Reports and Earned Value Management
2.5.2.5 Project Baselines
2.5.2.6 Project Change
2.5.3. Kanban Project
2.5.3.1 Set Up Kanban Projects
2.5.3.2 Configure Kanban Boards
2.5.3.3 Use Kanban Boards
2.5.4 Hybrid Agile Project
2.5.5 Hybrid Waterfall Project
2.5.6. Project Settings
2.5.6.1 Project Setup
2.5.6.2 Project Executions
2.5.6.3 Project Requirements
2.5.6.4 Project Builds
2.5.6.5 Project Tests
2.5.6.6 Project Docs
2.5.6.7 Project Releases
2.5.6.8 Project Reports
2.5.6.9 Project Risks
2.5.6.10 Project Issues
2.5.6.11 Project Opportunities
2.5.6.12 Project Deliverables
2.5.6.13 Project Reviews
2.5.6.14 Project Process
2.5.6.15 Deliverables
2.5.6.16 Quality Assurance
2.5.6.17 Project-specific Workflow Management
2.5.7 Project Templates
2.6. Execution
2.6.1 Product Planning and Task Breakdown
2.6.2 Task Assignment and Daily Tracking
2.6.3 Build Creation and Test Requests
2.6.4 Bug Confirmation and Resolution
2.6.5 Execution Kanban Boards
2.7. Testing
2.7.1 Write Test Cases
2.7.2 Execute Test Cases
2.7.3 Bug Submission and Reports
2.7.4 Verify and Close Bugs
2.7.5 Test Case Scenes
2.7.6 Submit a Test Request
2.7.7 Test Report
2.8. Agent
2.8.1 Conversation
2.8.2 Sanplex Agents
2.8.3 General Agents
2.8.4 Skill Management
2.8.5 AI Knowledge Library
2.8.6 Models
2.8.7 ZAI Service Installation
2.8.8 ZAI Service Control Panel
2.8.9 ZAI Configuration
2.9. Kanban
2.9.1 Kanban Spaces
2.9.2 Kanban Regions
2.9.3 Kanban Cards
2.10. Company
2.10.1 View Team Members and Work Information
2.10.2 View Recent Company Activity
2.10.3 View and Edit Company Information
2.11. Feedback
2.11.1 Configure, Create, and Review Feedback
2.11.2 Process Feedback and Send Notifications
2.11.3 Tickets
2.12. Admin Settings
2.12.1. System Settings
2.12.1.1 Mode
2.12.1.2 Backup
2.12.1.3 Trash
2.12.1.4 License
2.12.1.5 Security
2.12.1.6 Cron Job
2.12.1.7 Time Zone
2.12.1.8 Rebuild Index
2.12.1.9 LDAP
2.12.1.10 Table Engine
2.12.2 Feature Options
2.12.3. Users Management
2.12.3.1 Set Departments and Edit Company Profile
2.12.3.2 Manage Users
2.12.3.3 Set Permisions
2.12.4. Feature Configuration
2.12.4.1 Dashboard
2.12.4.2 Product
2.12.4.3 Project
2.12.4.4 Execution
2.12.4.5 Test
2.12.4.6 Kanban
2.12.4.7 Feedback
2.12.4.8 Tickets
2.12.4.9 User
2.12.4.10 Relations (Standard Version)
2.12.4.11 Meaturement
2.12.5 Migrate Jira Data to Sanplex
2.12.6 Jira to Sanplex Migration Mapping
2.12.7 Migrate Confluence Data to Sanplex
2.12.8. Agent Configuration
2.13. Asset Library (Premium)
2.13.1 Asset Library Management (Premium)

Manage Permissions

2026-04-13 15:27:54
Sanplex Content
456
Last edited by Jing WANG on 2026-10-15 19:04:00
Share links
Summary: Learn how to manage permission groups, configure accessible views and objects, assign action permissions, review dependent and recommended permissions, and manage Restricted User, guest, and Project Admin permissions in Sanplex.

Catalog

Under Admin > Users > Permission, administrators can manage permission groups and configure the access and actions available to each group.

The Actions column provides controls for managing each permission group:

  • View Permissions: Configure which views and objects the group can access.
  • Assign Permissions: Configure the actions and operations that members of the group can perform.
  • Manage Members: Manage the users assigned to the permission group.
  • Edit Group: Modify the group information.
  • Copy Group: Create a new group based on an existing permission group.
  • Delete Group: Remove the permission group.

Admin > Users > Permission page showing permission groups with Group Name, Description, Group Members, and action icons for managing each group.

I. View Permissions

Click the View Permissions action for a permission group to configure which Sanplex areas and objects its members can access.

Permission group list with the View Permissions action highlighted in the Actions column.Permission group list with the View Permissions action highlighted in the Actions column.

1. Accessible Views

On the View Permissions page, use Accessible Views to select the Sanplex areas that members of the permission group can access.

Available views include areas such as Program, Product, Project, Execution, Test, Agent, Kanban, Document, Company, Admin, Feedback, and Asset.

You can select individual views or use Select All.

View Permissions page showing Accessible Views with Sanplex areas such as Program, Product, Project, Execution, Test, Agent, Kanban, Document, Company, Admin, Feedback, and Asset selected.

Clear a view to remove access to that area for members of the permission group. For example, if Test is cleared, members of the group will not have access to the Test view.

Accessible Views section of the View Permissions page with the Test checkbox cleared while other views remain selected.

2. Accessible Programs, Products, Projects, and Executions

In addition to views, you can restrict access to specific:

  • Programs
  • Products
  • Projects
  • Executions

For example, in Accessible Products, select Sanplex Free to limit the group to that product.

If an access field is left empty, Sanplex applies no access restriction for that object type, as indicated by the message Empty means no access restrictions.

The same configuration applies to Accessible Programs, Accessible Projects, and Accessible Executions.

Object access also works together with the action permissions assigned to the group. Users must have the appropriate permission to perform operations on the objects they can access.

View Permissions page with the Accessible Products list expanded and Sanplex Free selected, along with Accessible Programs, Projects, and Executions fields.

II. Assign Permissions

Go to Admin > Users > Permission, then click the permission action for the group you want to configure.

Permission group list with the permission action highlighted in the Actions column for configuring a group’s permissions.

1. Assign Permissions

The permission configuration page allows administrators to control actions at the module and permission-set level.

Permissions are organized by Sanplex areas and modules. Select or clear individual permissions according to the responsibilities of the group.

For example, if Add To-do is cleared, members of the group will not have permission to add to-dos.

Permission configuration page showing the To-do module with Add To-do cleared while other To-do permissions remain selected.

Use the module tabs across the top of the page to move between permission areas such as Dashboard, Program, Product, Project, Execution, Test, Agent, Kanban, and Document. Additional areas are available under More.

The controls in the upper-right corner of the permission area allow you to switch how permission sets are displayed.

Permission configuration page showing module tabs across the top and display controls for viewing permission sets.

2. Dependent Permissions

Some permissions depend on other permissions to work together correctly.

When a selected permission requires related access, Sanplex displays the corresponding permissions in the Dependent Permissions panel on the right side of the page.

This helps ensure that the permissions required by the selected configuration are included.

Permission configuration page showing the Dependent Permissions panel with related permissions for Story, Feature, Task, and Case Library.

3. Recommended Permissions

Sanplex also provides Recommended Permissions based on the current permission configuration.

These permissions are displayed separately from required dependencies so that administrators can review additional permissions that may be useful for the group.

For example, the panel can recommend related permissions for Epic, Product settings, Story, or Feature.

Select the recommended permissions that are appropriate for the responsibilities of the group.

Permission configuration page showing the Recommended Permissions panel with optional permissions for Epic, Product settings, Story, and Feature.

III. Permission Descriptions

1. Restricted User Group

The Restricted User group is intended for users who should have limited editing permissions for related content.

Permission group list with the Restricted User group highlighted and described as Related Content Editing Only.

Users in this group can edit items related to themselves, such as stories, tasks, and bugs, while creation and other operations are restricted according to the permissions assigned to the group.

“Related to themselves” includes items that are:

  • assigned to the user;
  • completed by the user;
  • canceled by the user;
  • closed by the user; or
  • last edited by the user.

Items on which the user is only copied are not considered related content.

If an existing user is added to the Restricted User group, the relationship between that user and previously created or processed items remains available for permission evaluation.

The Restricted User group configured under Admin > Users > Permission applies at the system permission-group level. Restricted access configured within a specific project or execution applies to that corresponding scope.

This group can be used when users should work only with content directly related to their responsibilities.

2. Product, Program, Project, and Execution Permissions

Permission groups work together with the access controls configured for individual programs, products, projects, and executions.

Product Access Control

  • Public: Users with the appropriate product permissions can access the product.
  • Private: Access is limited to the users associated with the product and related work.
  • Whitelist: Access can be granted to specified users.

Top-level Program Access Control

  • Public: Users with the appropriate program permissions can access the program.
  • Private: Access is limited to the program owner and related stakeholders.

Sub-program Access Control

  • Fully public: Users with the appropriate program permissions can access the sub-program.
  • Public within program: Access is available within the corresponding program scope.
  • Private: Access is limited to the sub-program owner and related stakeholders.

Independent Project Access Control

  • Permission Control:
    Inherit: Uses the applicable inherited permissions together with the project configuration.
    Redefine: Uses the permissions defined for the project.
  • Access Control:
    Public: Users with the appropriate project permissions can access the project.
    Private: Access is limited to the project team and related stakeholders.

Program-bound Project Access Control

  • Permission Control:
    Inherit: Uses inherited permissions together with the project configuration.
    Redefine: Uses the permissions defined for the project.
  • Access Control:
    Fully public: Users with the appropriate project permissions can access the project.
    Public within program: Access is available within the associated program scope.
    Private: Access is limited to the project team and related stakeholders.

Execution Access Control

  • Inherit from project access: Users with access to the project can access the execution according to the inherited configuration.
  • Private: Access is limited to the execution team and other users included by the corresponding project or execution configuration.

3. Guest Permission Group

Sanplex provides a Login as Guest setting for controlling guest access.

Go to Company > Company and click Edit to configure Login as Guest.

Company > Company page showing Company Info, the Edit button, and the Login as Guest setting currently set to Disable.

The guest permission group is available under Admin > Users > Permission. Configure the permissions assigned to this group to control the areas and actions available through guest access.

Permission group list with the guest group highlighted in Admin > Users > Permission.

4. Project Administrator Permission Group

The Project Admin permission group provides a convenient way to assign selected users management access to specified Sanplex objects.

On the permission group list, locate Project Admin and use the Manage Project Admin action.

Permission group list with the Project Admin group highlighted and the Manage Project Admin action shown in the Actions column.

On the Project Admin management page, select the Group Users and configure the Manageable Objects that each user is allowed to manage.

Manageable object types include:

  • Programs
  • Projects
  • Products
  • Executions

You can select individual objects for each type. Use the corresponding All checkbox to allow the user to manage all objects of that type.

Click Save after completing the configuration.

Project administrator management page showing Group Users and Manageable Objects for Programs, Projects, Products, and Executions, with All checkboxes for each object type.

Write a Comment
Comment will be posted after it is reviewed.