As paid users know, PBworks has a very flexible security system. Using custom page- or folder-level security, you can specify exactly who can view or edit a page, down to the individual user.
However, until now, there has been one downside to applying Custom Security settings. These security settings have been exclusive. That is, once you specified Custom Security, only those people you explicitly added would have access to the page or folder.
This is fine for many uses, but it is difficult when you want to expose a particular page to a particular user without affecting how other people access the page.
Here’s an example: Let’s say I’m working on a new case study. When I’ve written the content, I want the customer who is the subject of the case study, Jane, to be able to review the page and make her edits.
Under the classic Custom Security system, I could set up Jane as a page-level only user and then add her to the case study page. However, this would also prevent any non-admins from viewing the case study, cutting off folks like Alexis and Sam from the PR team. To maintain Alexis and Sam’s access, I’d either have to explicitly add them as users, or make them workspace administrators.
Adding them as users under Custom Security is a hassle, and making them administrators may not necessarily be appropriate or viable.
Enter Additive Security. Now, when you set up Custom Security on a page or folder, you can add Jane as a user without changing anyone else’s ability to access the page.
Plus, you can always use “Who can see this?” to see an explicit list of everyone who has access to the page or folder.
Additive Security makes it even easier to use PBworks to collaborate with people outside your organization. For more details and illustrated instructions, check out our user manual: