Examples

some inline examples below in permissions+howto

 

How To

Table of Contents

1. Individual card permissions
1. Permission to create cards
2. Default card permissions
3. Global permissions

Individual card permissions

 

Go to the Options tab of any card, and you'll see a list of the four actions that can be taken with a card: read, edit, delete, and comment. If you can "set card permissions" (see Global Permissions below), you will see a dropdown menu beside each action, enabling you to set which Role can perform that action on that card.

 

• Read — a card that a user can't see will not show up in search results, will show a denial message if navigated to, and will not show up when included. Links to it will still show up as pointing to an "existing" card.
• Edit — This lets you edit not only a card's content but also its name and cardtype.
• Comment — sets who can comment on a card. If "Nobody," then no comment box appears for anyone. Cannot be used on hard formatted cards.
• Delete — determines who can delete a card

 

For example, if you want anyone to be able to edit a card even if they're not signed in, go to it's Options tab, click on the menu to the left of "...can edit this card", select "Anyone" and click "Save Changes".

 

If you are not able to set card permissions, then instead of menus in the Options tab, next to each action you will see the Role that currently has permission to take that action.

 

 

Permission to create cards

Create permissions are set by Cardtype. In the Options tab of cardtype cards, you'll see a fifth dropdown menu, next to "...can create cards". This lets you control who can create cards of that cardtype.

 

 

Default card permissions

 

Card permissions on a newly created card are set by the relevant type form. For example, if you format User cards by setting User+*tform so that Anyone can read it, Anyone Signed In can edit it, and Administrator can delete it, then any new User card will have those permissions, too. If you create a card of a type that has no +*tform, its default permissions will be set by Basic+*tform. After creation, read, write, and edit permissions on any card can be changed independently (even if they were set by hard form).

 

Default read permissions on newly created plus cards are set by their parts (all other permissions come from the relevant formatting card, as described above). If the left and right parts have different read permisions, the new card will take the more restrictive permissions. So, if "John Doe" is readable by Anyone, and "biography" is readable by Anyone Signed In, then by default "John Doe+biography" can be read by Anyone Signed In. If the two read permissions are different but equally restrictive — all roles but "Anyone" and "Anyone Signed In" are considered equally restrictive — then the leftmost card's permission wins.

 

 

Global permissions

 

The following permissions can each be assigned to one or more Roles. Each account can, in turn, be assigned one or more roles, and has all of the global permissions that have been assigned to any of Role given to that account. You will be able to set global permissions only if your account has a Role that has the permission to set global permissions.

 

All of these are automatically given to the Administrator role.

• set global permissions — the power to assign any of these global permissions to any Role. This is the most powerful permission and should generally not be given to any role.
• set card permissions — the power to determine who can view, edit, delete, comment on or create cards, by setting individual and default card permissions (see above)
• administrate users — the power to block Users, change their email address, and reset their passwords (all on their Options tab)
• create accounts — the power to give out accounts by approving requests (they must also be able to see Account Requests), and by adding accounts to existing cards
• assign user roles — the power to assign any Role to any User (using their Options tab). This is equally powerful to set global permissions, and should generally not be given to any role.

If you have the Administrator role, then at the bottom of the sidebar you will see an "Administrator links" card — which includes links to administrate accounts and roles, and to set these global permissions.

 

 

Tips

For Developers: the api to change permission on a specific task on a specific card is as follows:

card.permit(task, party)

eg. @card.permit(:read, Role[:anon])

tasks include read, edit, delete, comment and (on Cardtypes) create

 

Add +discussion