From Documentation

Jump to: navigation, search



One of the most concerned issues is access control for ZSS. We think most enterprises have their own authorization rule. Therefore, ZSS doesn't have its own authorization and authentication features because one feature can't fulfill all kinds of requirements. Instead, it provides 3 categories of API to help you build your own user permission mechanism:

  • show/hide UI
  • enable/disable functions
  • sheet protection

We will demonstrate the usage of API with a simple application. In this application, you can log in with 3 different roles: OWNER, EDITOR, VIEWER. Their permissions are described in the image below:


If you log in as an owner, you will have full control of the file. But if you log in as an editor, you will find all sheet related operations are disabled.


When you log in as a viewer, the only thing you can do is viewing. Because there is no UI for edit, and all sheets are protected from editing.


This application relies on those API we mentioned in previous chapters to control the access for each role. Let's recap them here:

Hide User Interface

Working with Spreadsheet/Control Components



Disable Functions

Working with Spreadsheet/Advanced/Disable Functions


spreadsheet.disableUserAction(AuxAction.COPY_SHEET, true);

Protect a Sheet

Working with Spreadsheet/Handling Data Model/Protection


                true, true, false, false, false, false, false,
                false, false, false, false, false, false, false, false);

You can download the example source code to know the complete implementation.

All source code listed in this book is at Github.

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.