Skip to main content
Skip table of contents

Saved Table Limits

You can configure limits on the number of tables users can save. If users reach their limit on saved tables, then they will have to delete some tables from Saved Tables before they will be able to save any more tables.

Overview of Saved Table Limits

  • SuperWEB2 has no default limits; if there are no limits configured then there will be no restriction on how many tables a user can save.
  • The limits are defined on a per group basis, so they only apply to users who belong to groups, although the actual limit is applied to each user individually, not shared between all users in that group. For example, if a group is limited to 50 tables then every user in that group will be able to have 50 saved tables at a time.

    If you have not already done so, you will need to organise your users into groups before you can configure saved table limits. See Users, Groups and Permissions for more information about this step.

  • If a user belongs to multiple groups, then whichever group has the lower limit will apply.
  • If the limit for a particular group is lowered and a user already has more saved tables than the new limit, then that user will not be able to save any new tables. The user will have to delete enough tables to get back under the configured limit before saving any new tables.
  • Saved table limits only apply to private saved tables, not to shared saved tables (tables that are saved to shared folders, accessible by multiple users).
  • Saved table limits are configured in SuperADMIN. There is no need to restart SuperWEB2 when you make changes; your changes are applied immediately. However, please note that:
    • If a user currently has the dataset open then the new limit will not apply until that user reselects the dataset from the catalogue.
    • Any changes to users and groups are not applied until users log out and back in again. So if you have just changed group memberships (with the account command) as part of setting up the saved table limits, then those changes will not be applied until the affected users log in again.

Configure Saved Table Limits

Saved table limits are configured in SuperADMIN.

Before starting to configure the limits, use the following command to check whether any current limits are defined:

cfg global superweb2.saveTableLimits

SuperWEB2 will either display the list of existing saved table limits (if some are already defined), or display "not found".

Scenario A: No Existing Limits Defined

If there are no existing limits defined, SuperADMIN displays the message "not found":

> cfg global superweb2.saveTableLimits
superweb2.saveTableLimits: not found

You can add a new limit using the following commands:

cfg global superweb2.saveTableLimits[<index>].groupId set <group>
cfg global superweb2.saveTableLimits[<index>].limit set <limit>


  • <index> is the index for this group limit. Each group limit has a unique index number, starting from zero.
  • <group> is the ID of the group this limit applies to. You can obtain a list of group IDs by using the SuperADMIN command account groups.
  • <limit> is the number of tables that users who belong to this group will be able to save.

For example, the following commands specify that users who belong to the users group will be able to save a maximum of 50 tables. As this is the first rule defined it has the index value of 0.

cfg global superweb2.saveTableLimits[0].groupId set "users"
cfg global superweb2.saveTableLimits[0].limit set 50

To add a second rule, use the same commands but increment the index value. For example:

cfg global superweb2.saveTableLimits[1].groupId set "administrators"
cfg global superweb2.saveTableLimits[1].limit set 100

Scenario B: Existing Limits Defined

If there are already some existing limits defined, then SuperADMIN displays the details. For example:

> cfg global superweb2.saveTableLimits
superweb2.saveTableLimits :

In this example there are two existing sets of limits defined, one for a group called users and one for a group called administrators (each one is enclosed in curly brackets).

You can either add a new set of limits or update one of these existing ones:

  • To add a new rule, simply make sure that you use the next index value up. In this example, there are already two rules, so to create a third rule you must use the index value of 2 (because the index numbering starts at 0). For example:

    cfg global superweb2.saveTableLimits[2].groupId set "managers"
    cfg global superweb2.saveTableLimits[2].limit set 50
  • To update an existing rule, simply use the index value of the existing rule. For example, to update the limit setting for the second rule (the administrators one), use the index value of 1:

    cfg global superweb2.saveTableLimits[1].limit set 150

Remove Saved Table Limits

If you want to remove a saved table limit, use the following command:

cfg global superweb2.saveTableLimits[<index>] remove

For example, to remove the second limit, use the following command (the second limit has the index value of 1, because the numbering starts at 0):

> cfg global superweb2.saveTableLimits[1] remove
superweb2.saveTableLimits[1] : Removed

When you remove a limit, the index values of any subsequent limits will be updated accordingly to replace the removed one. For example, if you have three limits defined, their index values will be 0, 1 and 2. When you remove the one with index value 1, the index value of the third one will be updated from 2 to 1.

If you want to remove all the saved table limits, use the following command:

cfg global superweb2.saveTableLimits remove
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.