how do i stop my users sharing the wiki?
i have a private wiki and only want the users who i set up to be able to read and use the wiki.
I do not want these users to then go and invite others to read it.
is there any way to disable/remove the "share this wiki" link please?
(by the way i had to log this call using firefox as ie7 had javascript errors)
I do not want these users to then go and invite others to read it.
is there any way to disable/remove the "share this wiki" link please?
(by the way i had to log this call using firefox as ie7 had javascript errors)
6
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
These are really good issues and some helpful suggested resolutions. As the CEO I'm also the interim "product manager", so this input is going to help us make sure that people can easily share a wiki where that's intended but allow an administrator to limit such sharing. I think you'll find many of these issues addressed with our tighter access controls in 2.0, but we'll need to make sure this is the case. Sorry again to have created a surprising situation in 1.0.
3 people say
this answers the question
The best answer from everyone
-
OK - here are a couple of suggestions.
1. Provide the wiki's administrator with the means to prevent the 'share this wiki' links being displayed. We can already delete the 'Quicklinks' page to remove that access point but there's no obvious way to get rid of the link in the 'Wiki information' section at the bottom of the page.
2. And this could be used in conjunction with 1 – let the wiki administrator set the level of access that contributors can provide to friends/colleagues via the 'share this wiki' page. If for example you were to set contributors sharing rights to none, the sharing page would still be accessible but there would be no capacity for users to 'do anything' once there.
Regards,
Terry...
3 people say
this answers the question
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I failed to get a meaningful response from support when I asked them this same question (you can 'get rid' of the share link in the quickstart panel by simply deleting the quickstart page but there is no obvious means for deleting the link in the 'wiki information' section at the bottom of each page. Honestly, what's the point of having a private wiki if your contributors can go and provide editing access to absolutely anyone with a valid email address. Guys, you really need to let administrators toggle this feature off and on.
Terry...
I’m annoyed!
-
Inappropriate?Thank you for providing this feedback. I'm sorry we didn't answer sooner, but we've actually been bouncing emails back and forth on our end trying to figure this out, and right now, we don't have a good solution.
For starters though, it's in human nature to figure out ways of doing things they shouldn't. So if your readers, no matter how many guards you put around them, *really* want to share what's in the wiki, whether it's by sending the URL, copying and pasting the content, or having people look over their shoulders when they're on the wiki, they will find a way.
However, some things you can do:
1. Communicate with your users. Help them understand how important it is to keep this information private. You know they're excited about what they do, but some secrets are better staying secrets. Be open about what they can and can't share, and they'll be better able to do their jobs, because they'll know where they stand.
2. Make sure they have PBwiki Accounts and don't use the invite keys, so you can adjust their levels of access to your wiki, and if they leave, you can close that hole in security by just removing their access altogether.
If you really want to step things up a level, and the sensitivity of your information is so high you need all the security you can get, you also have the following options to exercise:
-Sign up for a premium plan that lets you use IP whitelisting, so your users can only log in from certain IPs. There are even more security benefits to having a premium plan, and I encourage you to look into those as well.
-Have them sign Non-Disclosure Agreements so that you have the option of legal recourse should they divulge information.
However, these two things fall on the side of you not being able to trust your users, and that's not a good situation to be in ever. So personally, I recommend trying the first two things before the second. A culture of fear and restriction is hard to live in, work in, and be productive and creative in. -
Inappropriate?Thanks for asking this question, we've been discussing it internally and we'd love to hear what you think might be the best way to implement this feature.
I’m glad we're talking about this
1 person says
this answers the question
-
Inappropriate?OK - here are a couple of suggestions.
1. Provide the wiki's administrator with the means to prevent the 'share this wiki' links being displayed. We can already delete the 'Quicklinks' page to remove that access point but there's no obvious way to get rid of the link in the 'Wiki information' section at the bottom of the page.
2. And this could be used in conjunction with 1 – let the wiki administrator set the level of access that contributors can provide to friends/colleagues via the 'share this wiki' page. If for example you were to set contributors sharing rights to none, the sharing page would still be accessible but there would be no capacity for users to 'do anything' once there.
Regards,
Terry...
3 people say
this answers the question
-
Inappropriate?Terry makes some good suggestions. I would go along with these.
We already use white listing so only people within the building can see the wiki but we want stricter controls on all the users so we know only the users who the administrator invites are active.
Things involving security (like this does) should take highest priority in order to help your private and business users feel more secure about their information.
-
Inappropriate?Whitelisting is a nice feature but not particularly useful in tertiary education settings (such as ours) where students are increasingly working online but off-campus.
Terry... -
Inappropriate?To me, the act of making a wiki "private" should automatically disable the "share this wiki" link. Not everyone in my company is as sensible as they should be...
1 person says
this answers the question
-
Inappropriate?These are really good issues and some helpful suggested resolutions. As the CEO I'm also the interim "product manager", so this input is going to help us make sure that people can easily share a wiki where that's intended but allow an administrator to limit such sharing. I think you'll find many of these issues addressed with our tighter access controls in 2.0, but we'll need to make sure this is the case. Sorry again to have created a surprising situation in 1.0.
3 people say
this answers the question
-
Inappropriate?If you want to make sure only approved users are accessing your wiki, have them all create PBwiki accounts, change the Invite key so no one can use that as a back door, and by going to Settings | Users as the Administrator, manually add each person via the email they used with their PBwiki Account to the wiki. That way, you can control their level of access to the wiki, and remove them entirely if they leave the company. Also, it makes adding new people to the wiki that much easier.
As an added bonus, you can see who made each edit on the page because they will have had to log in with their account - no more "anonymous" edits.
By the way, thank you for your feedback, really. This is something we're taking very seriously, and we appreciate you telling us about the situation you're in, because it will only help us make PBwiki better for you.
I’m liking constructive criticism.
-
Inappropriate?Casey - thanks for the suggested workaround, unfortunately with over 1000 potential users it's just not practicable in our case.
Terry...
Loading Profile...






EMPLOYEE