Organization membership
Users must belong to the organization to access its workspace. Administrators manage member access.
Access that follows your organization structure
Make workspace and table access easier to understand
Learn how DataGridly organization membership, roles, and table-level permissions help administrators manage who can read, create, update, or delete records.
DataGridly uses organization membership and roles together with table permissions. Administrators can review which members can access a table and which record operations are allowed.
Organization roles and table permissions screenshot
Replace with the user management and table permission screens, using example accounts only.
Access model
Understand the controls available to administrators
Make permission decisions from the level of the team down to the table it needs to use.
Organization roles
Roles distinguish organization administration from member access and responsibilities.
Table-level permissions
Permissions can control whether a user may read, create, update, or delete records in a selected table.
Public links are a separate decision
A public share link can expose selected table data outside the organization. Review its scope and sharing settings before distributing it.
Rollout checklist
Review access as the workflow changes
A small permission review helps keep access aligned with who is responsible for each step.
List the people and responsibilities
Identify the organization members who need access and the work each person performs.
Set the least broad table access that fits
Decide who needs read, create, update, and delete access for each table.
Test with a member account
Confirm that a user sees the tables and actions intended for their role.
Review changes periodically
Revisit membership and table access when roles, processes, or external sharing needs change.
Common questions
What to know about security & permissions
Can I manage permissions for each table?
Yes. Table-level permissions support read, create, update, and delete access decisions.
Are field-level permissions described here?
No. This page covers organization roles and table-level access. Do not assume individual fields have separate permissions.
Does a public share link use the same access boundary?
Public sharing is intended for selected external access, so review the link’s table scope and settings independently from organization membership.
Does this page make a compliance or encryption certification claim?
No. Confirm current security documentation and contractual requirements with DataGridly before a regulated or sensitive-data rollout.
Continue exploring DataGridly
See it with your workflow
Need to review a specific access model?
Describe your organization, table structure, and access requirements so the right setup can be discussed.