WPS View Permissions is an Android multidimensional table feature for controlling who can see each view; it includes 1 core task, with 1 available without membership and 0 membership-related items.
At a Glance
| Metric | Value | Notes |
|---|---|---|
| Core tasks | 1 | Matches the number of rows in the How-to Index |
| Available without membership | 1 | Matches the number of Free rows in the index |
| Membership-related items | 0 | Matches the number of membership-related rows in the index |
About This Feature
Overview
View Permissions is a built-in feature in WPS Office for Android multidimensional tables that lets you manage visibility for each view separately within the same table.
Main capabilities:
- Set permissions for each view independently.
- Choose between two visibility options: visible to everyone in this view, or visible only to yourself.
- Save quickly by tapping a blank area after making a selection.
This feature is useful for team collaboration, separating sensitive information, and sharing different views with different roles while keeping the same underlying table.
System Requirements
| Item | Requirement |
|---|---|
| Operating system | An Android device that can run WPS Office normally |
| App version | It is recommended to use the latest version of WPS Office |
| Network | A network connection is recommended when opening online multidimensional tables and syncing permission changes |
| Other | You need access to the target multidimensional table and the related collaboration permissions |
Download & Installation
| Item | Details |
|---|---|
| Official download | WPS Office Free Download |
| Post-installation check | Open WPS Office, enter a multidimensional table, and confirm that the View Permissions entry is available under Tools |
Source: WPS download page
Compare with Alternatives
| Dimension | WPS | Microsoft | Notion | Adobe | |
|---|---|---|---|---|---|
| Capability Summary | Supports setting visibility for an individual view in an Android multidimensional table, with separate options for visible to everyone or visible only to yourself. | Microsoft Lists and SharePoint document list-, library-, and item-level permissions, but the official permissions page does not describe separate permissions for an individual view. | Google Sheets supports protected sheets and ranges for edit control and also supports hidden sheets, but the official help page states that hidden sheets are not a security measure and viewers can still access the content. | Notion databases support structure controls, view management restrictions, and row or page-level access, but database settings apply to the whole database rather than acting as a direct per-view visibility permission in the main database. | Adobe Acrobat supports sharing documents for viewing and protected document access, but it is designed for PDF viewing workflows rather than multidimensional table view permissions. |
| WPS Advantages | Advantage: WPS focuses directly on view-level visibility inside the same table, which is practical when different collaborators need different views of the same data. | Compared with WPS: permission controls focus on list, library, folder, or item scope instead of a dedicated view visibility setting. | Compared with WPS: controls are centered on editing protection and display hiding, not a dedicated view visibility model for shared table views. | Compared with WPS: stronger for database structure governance and row/page access, but the main database view permission model is different. | Compared with WPS: suited to PDF sharing and viewing, not table-view collaboration. |
| Official Source | — | Customize permissions for a SharePoint list or library | Protect, hide, and edit sheets | Assign custom database permissions | Share documents for viewing only |
Overall Conclusion
If your main goal is to control who can see specific views inside one shared multidimensional table, WPS provides a more direct workflow for that scenario. The other products focus more on list-level, page-level, edit-protection, or document-sharing controls.
Use Cases
| No. | Scenario | Suitable users | Main challenge | How View Permissions helps |
|---|---|---|---|---|
| 1 | Team-based viewing | Project members | Different members only need to see the views related to their work | Set a separate visibility rule for each view |
| 2 | Sensitive information separation | Managers | Some views should stay private even when the table is shared | Set sensitive views to visible only to yourself |
| 3 | Preparing an external-facing view | Collaboration owners | Internal views should stay hidden before sharing the table more broadly | Keep only the external-facing view visible to everyone |
| 4 | Personal working views | Individual contributors | Personal filtered views should not affect what others see | Keep personal views visible only to yourself |
| 5 | Multi-role collaboration | Operations and support teams | Different roles focus on different subsets of the same data | Create role-based views and manage visibility separately |
Membership & Benefits
Free vs WPS Premium
| Capability | Free users | WPS Premium |
|---|---|---|
| View permission settings | ✅ Available | ✅ Available |
| Core office features | ✅ Available | ✅ Available |
| Additional advanced features and expanded benefits | Based on the product interface and plan details | Includes more advanced features and broader benefits |
Source: WPS Office pricing page
Recommendations
| Scenario | Recommended plan | Why |
|---|---|---|
| You only need to manage view visibility on Android | Free | This feature can be used without membership |
| You also need more advanced office or collaboration benefits | WPS Premium | Suitable if you use broader premium features across WPS Office |
How to Subscribe
- Subscribe through the WPS Office pricing page
Source: WPS Office pricing page