Creating an application activity permissions table
- Last Updated: January 17, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
You create a permissions table within the Data Dictionary. These topics call
the table permissions, but you can use any name you want. Each record in the permissions table
contains at least two fields: an activity field and a can–run field. The activity field
contains the name of the procedure and the can–run field
contains a comma-separated list of the user IDs of those users who have permission to run the
procedure. (Whether these are database connection or OpenEdge session IDs depends entirely on
how you match them with the CAN-DO function.) Normally, the
primary index is built on the activity field.
After you create a permissions table, you must add a record for every application activity for which you want to provide security.