Topic: Writeboard password from Basecamp?

Aha. You can’t change the password because that feature seems to be missing from a Writeboard that was set up through Basecamp.

Topic: Writeboard password from Basecamp?

For anyone who’s interested, a workaround is to grab the URL of the Writeboard and try to open it in a new browser window. At the login dialog, leave the password field blank and click “Sign in”. The resulting error message gives you the option of emailing the password to the creator of the Writeboard, in this case me.

Since the system-generated password is more secure (i.e. complex) than I would like for a one-off job, I’m experimenting with whether it’s possible to change the password and still have the Writeboard recognised by Basecamp.

Topic: Writeboard password from Basecamp?

Having created a Writeboard via Basecamp, can I find its password? I would like to be able to send the Writeboard’s URL (obvious to me) and password (not obvious) to people who are not listed on my Basecamp system.

This might sound a bit perverse, but I have a good reason. As a technical journalist, I often need to show a draft article to a bunch of people I’ve interviewed. Since this is usually a one-off process, I’d rather not enter their details into Basecamp. On the other hand, creating the Writeboard through Basecamp, as opposed to a stand-alone Writeboard, helps me keep Writeboards organised by client, so the companies I work for can easily see all the drafts relevant to them.

As a subsidiary question, is there a way to get Basecamp to show that a Comment has been added to a Writeboard? The only workaround I have found is to make a minor change to the Writeboard itself, delete the change, and save. Slightly closer integration with Basecamp would be nice.

Topic: Where to keep files common to more than 1 project?

I have the same problem. We have several customers that need essentially the same group of base files. I emailed your support on this the other day. Here’s a copy of the email that explains our problem.

BEGIN EMAIL
I have a request to make if you don’t already offer this feature and I’ve somehow missed it.

Our usage of Basecamp has been low, but with some recent changes we’re making I expect that will increase a great deal which creates a problem for us. Our customers need to work on documents with us and in many cases a bunch of different customers need access to the same basic document. The problem comes when that document, or set of files, gets updated. If I have 20 different customers with 10 internal groups per customer (doesn’t even come close to what we’ll need) and they all need an update to the same files I/We have a lot of work to do.

It would be nice to have some sort of a shared file or project that I could assign access to. I realize I could just create a project and allow everyone to access it but not everyone should see each other. Sort of like a project where users can’t see each other, only the admin can see those that have access.

Make sense?

Thanks for a couple of excellent tools in Basecamp and Highrise.

Topic: Where to keep files common to more than 1 project?

Why not create a project called “Common Files” or “Files” or something like that and put them all in there. You could also put common messages, common announcements, etc in there.