Query security is set for each query individually by the Query creator, or the Query modifier. You can see all of your security options on the Security tab of each individual query.
Note: This Security tab is available only if the QuerySecurity system option is set to true.
Query security is based on an initial choice. You must choose one of the following and then set your specifics from there:
You can then choose to deny or allow a user group, or many user groups, the ability to view and run a query from the Query Tool and Query Central.
If you want to deny most users and allow just a few groups, use the following steps:
If you want to allow most users and deny just a few groups, use the following steps:
Example: If a user is in Groups A, B, and C, and the query is denied to Groups A, B, and Z, then the user is able to run the query because he or she is in Group C. If a different user is in only Groups A and Z, then he or she is not able to run the query.
Queries observe Group Table Privilege and Group Column Privilege setup. Even if the user can run a query, if the user does not have select access to a Table or Columns then they won't be allowed to use them in the query.
Q. What happens if a user loads an audience containing a denied query?
A. Audience observes query security. If a user loads an audience containing a denied query, then that query block is empty and the audience does not function as intended.
Q. Is there a way to prevent a user from modifying a saved query? Can they be allowed to run the query, just not modify it.
A. The only way to do this is to put users in Groups that can access Query Central but not the actual query links to the query designer. If you do this, however, these users will not be able to develop any of their own queries.
Q. Does Query Security work through xWeb?
A. Query Security applies as well to the GetDynamicQuery web method, based on the xWeb User.