Loading Profile...
Rolling out our wiki internally
I have set up our wiki to allow access to anyone with an @ourcompany.com email. I'm unclear how to publicize this to our company. This is a private wiki for internal use only.
When i had an employee test this, this is how she responded:
There is the Wiki password/invite key and then an opportunity to put in your name and e-mail. I tried my e-mail as the key and then my name and e-mail and it says that my invite key is not valid.
If you have a PBwiki account, you can put in your e-mail and a password.
What am I doing wrong?
When i had an employee test this, this is how she responded:
There is the Wiki password/invite key and then an opportunity to put in your name and e-mail. I tried my e-mail as the key and then my name and e-mail and it says that my invite key is not valid.
If you have a PBwiki account, you can put in your e-mail and a password.
What am I doing wrong?
I’m confused
1 person has 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.
-
Inappropriate?We have similar issues where I work, especially since everything is, as you say, internal. Normally, some sort of internal mailing list is used to make internal announcements, but some companies have restrictions on how those lists are used. If this is part of a legitimate corporate initiative, then the person who assigned you the task would be the best person to ask about publicizing it. If it's not an official project, then you might be better off checking with your supervisor or HR person before doing anything. Many companies have policies regarding the use of outside tools like PBwiki, especially for potentially confidential or proprietary information. Not that there's anything wrong with PBwiki's security, but someone in management may want to verify and sign off on this activity before it's widely deployed. -
Inappropriate?To clarify, my issue is not with policy. It is with the technology. I have set the system up to make it accessible, but I don't know how to instruct people to access it. When I had someone test it, it did not work. -
Inappropriate?Hi Debra,
What your users will need to do is first create an account at my.pbwiki.com. They can then join your wiki. When you invite users to your wiki, we send out an e-mail with this information, but you may want to directly point them to my.pbwiki.com. If you have any specific information about what is not working just let us know and we'll work it out for you :) -
Inappropriate?Sorry Debra, I misunderstood. Are you trying to use the Access via Email feature? If so, I'll set it up on one of my wikis, and see if I can get it working.
-
Inappropriate?Hi Debra,
To invite people with access via e-mail, just send them a quick e-mail giving them the URL of the wiki. When they go to the wiki they will be prompted to log in with their email address. PBwiki will mail a specially encoded URL, and they'll receive Contributor access.
Just make sure you have gone into "Settings" and "Keys and Access" to set the Contributor password level -
Inappropriate?Actually, Debra, make sure they don't try to log in. Look down below the login fields, it should say something like:
Does your email address end with @domainxyz.com?
Send yourself a wiki invitation
They'll need to click the "Send youself a wiki invitation" link to trigger the URL email.
Hope this helps. -
Inappropriate?Ok. I'm getting closer. There is no password set under the keys and access setting, so i'm guessing that means so long as the email address is ok, they will get a link that is open. If I add a password, do I need to provide it to them or will that come with the url message?
-
Inappropriate?That should come encoded in the URL of the message once you set the password.
-
Inappropriate?To clarify: They will not receive the password in a form they can use. The message from PBwiki has a "magic" URL that encodes the password. If they click the "magic" URL, they will be logged in.
They will not be able to log in without the "magic" URL unless you give them the password separately.
If you change the password, any existing "magic" URLs will become invalid. -
Inappropriate?Thank you for the clarification. So, if employee leaves, I change the password so the magic url doesn't work anymore and the former employee can't access. What is the impact on the remaining users. Will a new url need to be circulated? What happens?
-
Inappropriate?You are correct - you would either need to send out a new url, or send out the new password. That's one of the advantages of using PBwiki identities to control access; if you use Identities to grant access, and someone leaves, you can just take away their access, and there's no need to notify everyone of a changed password/URL.
-
Inappropriate?Identities is part of 2.0 right?
-
Inappropriate?Nope. Identities are part of 1.0. I use them for all of my 1.0 wikis. As long as you're the only person on your computer, and you never have to log in as a different user, then Identities are wonderful. I highly recommend them.
-
Inappropriate?Sounds great. How do I find them?
-
Inappropriate?Go here, create an account, then visit your wiki, log in with the password, and it should add it to your list of wikis on my.pbwiki.com.
-
Inappropriate?At the risk of sounding completely insane, I'm going to go back to my original question. I'm rolling out our company wiki internally. I need to send a message so people can log in.
It sounds like
1) I should provide them with a URL to PB wiki,
2) instruct them to create an account and
3) then visit our actually wiki and it should add it to the list of wiki's on my.pbwiki.com?
that sounds like it will confuse people, no? -
Inappropriate?Yes, and that's the entire problem PBwiki has been wrestling with for the last year:
* Passwords are simple and easy to setup and use, but difficult to maintain when someone leaves
* Identities are a bit more complicated (not much), but much easier for a single admin to maintain.
If you don't anticipate a huge number of users, and turnover is low, and it won't be burdensome to inform everyone of a password change when some leaves, then use passwords.
Sorry it's so confusing.
EMPLOYEE