JavaScript required
We’re sorry, but Coda doesn’t work properly without JavaScript enabled.
Skip to content
Org-OS | The Source Platform
Org-OS | The Source Platform
Manifesto
TODO
Daily-Dev-Notes
Form-Generator
Architecture
Questions - Decisions
AI Instructions
Steps
Pricing
Biz-Dev-TODO
The-Source Investment Opportunity
The-Source Proposal for Small Businesses and Chamber of Commerce
Loans
Marketing
Stages of Growth
Proposal/Presentation for Foundations/Philanthropy
AI Coding Considerations
Field-Management
More
Share
Explore
Architecture
Permissions
Permissions
We make use of dynamic permissions a lot
Orgs and Groups are same but permissions based on OrgType
Group Visibility
Groups are hidden by default
Orgs are visible by default
Controlled by Org_Visbility
hidden
even if you have a direct link won’t acknowledge it exists
public
invite-only
shows that group exists and is invite only
they can request access for an admin to approve them
Members can always view the group
Org/Group Roles
Member
can view org members and posts
need the “Can-Post” permission to post
start date for viewing posts
so could only view posts after added
or can view previous ones
or only so far back
Admin
can edit data
can add, edit, delete all sub-records
Other Permissions
can invite new members
ie can add new person recs to the Org-Members table
only for Admins for now to keep it simple
Posts
Can post
ie Add Records
Edit Posts when Person listed in Post-Collaborators
for Events
Otherwise Only Admins can edit others posts
? Should we have a “Superuser” role for being able to edit other people’s posts
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
Ctrl
P
) instead.