Page Comparison

...

Note
We structure the permissions definitions in terms of questions to be answered. The permissions below are what we are actually implementing in the code right now.

, a checkbox means we have implemented it

Wall Post

Wall Context	Condition	create	comment	read	edit	delete	x
User	always	owner of wall	registered users	owner of wall	owner of post	owner of wall owner of post
	if profile visibility "public"			everyone
	if profile visibility "registered users"			registered users
	if profile visibility "communities"			communities of user
	if profile visibility "connected users"			users connections
	if profile visibility "private"
Group	always	members	members	members	owner of post	owner of post (more via teams)
	teams						with x wall action

Users in a group don't have any special permissions. To have any permission they need to be in a team with the appropriate action.

Type	Condition	create	delete	edit	join	manage teams	x
Community	always	registered users	users in team with "superadmin" action	users in team with "superadmin" action	registered users	users in team with "superadmin" action
All groups	always	users in group team with "create" action	users in group team with "delete" action				with x group action

Action	Description
edit	rename group, change description, change picture, change category of group, keywords, change region
manage teams	create new team, edit team, delete team, add action, remove action (note: at some point we need to distinguish which actions are able to be granted, e.g. POSSIBLY if you can "manage teams" yourself, this should not let you give others the "manage teams" permission... needs more discussion... can an admin make other people admin?)

When a subgroup is created, it will have some teams and actions created by default.

Team Name	create	delete	edit	manage teams
admin	✓	✓?	✓?
superadmin	✓?	✓?	✓?	✓?

if the wall is for a team, and the team is for a group, and that group has another team with "<some kind of special super admin>" permission, then:
- TBC