WPS Custom Roles is an advanced permission feature for databases on Windows; it includes 3 core tasks, with 3 available without membership and 0 membership-related items.
At a Glance
| Metric | Value | Notes |
|---|---|---|
| Core tasks | 3 | Matches the number of rows in the How-to Index |
| Available without membership | 3 | Matches the number of Free rows in the index |
| Membership-related items | 0 | Matches the number of membership-related rows in the index |
| Version requirement | No specific version limit listed | Available where Advanced Permissions is supported on Windows |
About This Feature
Overview
Custom Roles helps you create role-based permissions in a database so different collaborators can receive access based on their responsibilities. You can create a role, configure permissions across multiple tabs, and then assign collaborators to that role for consistent access control.
Core tasks include:
- Create a custom role for a new responsibility or team.
- Configure permissions for collaborators, data, dashboards, automations, and other functions.
- Add collaborators to a custom role so the selected permissions apply together.
System Requirements
| Item | Requirement |
|---|---|
| Operating system | A Windows PC that can run WPS Office normally |
| App version | The latest version of WPS Office is recommended, with access to database Advanced Permissions |
| Network | A stable internet connection is recommended when opening online databases and syncing permission changes |
| Other | You need permission to manage the target database and open the Advanced Permissions panel |
Download & Installation
| Item | Details |
|---|---|
| Official download | WPS Office Free Download |
| Installation | Install WPS Office for Windows, sign in, and open the target database |
| Check after installation | Open the database and confirm that the Advanced Permissions entry is available |
Source: WPS download center
Compare with Alternatives
| Dimension | WPS | Microsoft | Notion | Adobe | |
|---|---|---|---|---|---|
| Capability Summary | Create custom roles in a database and configure permissions for collaborators, data, dashboards, automations, and other functions. | Microsoft Entra supports custom roles with fine-grained permissions across available management categories. | Google Workspace supports custom admin roles by selecting privileges in the Admin console. | Notion provides workspace roles, teamspace roles, and page-sharing permissions for access control. | Adobe Admin Console supports custom roles with selected permission sets for users or user groups. |
| WPS Advantages | Advantage: role creation, permission setup, and collaborator assignment can be completed in one permission panel for database collaboration. | Compared with WPS: focused more on directory and identity administration than database collaboration permissions. | Compared with WPS: focused on admin-console responsibilities rather than role setup inside a collaborative data table. | Compared with WPS: centered on workspace and page permissions, not a single panel for data, dashboards, and automations together. | Compared with WPS: focused on enterprise console access management rather than table collaboration roles. |
| Official Source | — | Create a custom role in Microsoft Entra ID | Create, edit, and delete custom admin roles | Sharing & permissions | How to create custom roles |
Overall Conclusion
WPS is a practical fit when your goal is to manage collaborators and feature access directly inside a database workflow. The other products also support role or permission control, but their official guidance is more focused on workspace administration, identity management, or enterprise console management.
Use Cases
| No. | Scenario | Suitable for | Main issue | How Custom Roles helps |
|---|---|---|---|---|
| 1 | Department-based access control | Team leads | Different jobs need different access scopes | Create separate custom roles for viewers, editors, and managers |
| 2 | Dashboard sharing control | Analytics teams | Dashboard visibility and sharing need to be separated | Configure dashboard permissions inside the role |
| 3 | Automation governance | Process owners | Not everyone should create or delete automations | Limit automation permissions in the role settings |
| 4 | Faster collaborator assignment | Project admins | Assigning permissions one by one is inefficient | Add collaborators to a prepared role |
| 5 | Permission review | Data governance teams | Permissions are hard to review when scattered | Check role settings in one place before saving |
Membership & Benefits
Free vs WPS Premium
| Capability | Free | WPS Premium |
|---|---|---|
| Custom Roles basic operations | Available | Available |
| Core WPS Office apps | Available | Available |
| Some advanced value-added features | May be limited | More advanced features may be available |
| Cloud storage and extended benefits | Basic allocation | Higher allocation or more benefits |
Source: WPS Office pricing page
Recommendations
| Scenario | Recommended plan | Why |
|---|---|---|
| You mainly need to create and manage Custom Roles in a database | Free | The listed Custom Roles workflow does not require membership |
| You also need more PDF, AI, or extended office features | WPS Premium | A practical fit when permission management is part of broader advanced office work |
How to Subscribe
- Open the membership page: Subscribe to WPS Premium
Source: WPS Office pricing page