Topic: Thank you for Deals!

Agree.

Nice work guys… this has been a long time coming :D

No more pissing about with a Basecamp project and message categories.

WIN.

Topic: Close messages

As a workaround, we file each message on each project within a folder that move it through the live cycle ending with all messages at the end of the project indicated as “closed”. It’s a bit of organization to set up the folders but it seems to work for us for status of messages. We’d welcome any more automated way to accomplish this, Basecamp!

Miscellaneous Comments & Discussion
a. Specs and Input
b. Design: Closed Issues
b. Design: Open Issues
c. Copy/Production: Closed Issues
c. Copy/Production: Open Issues
d. Programming: Closed Issues
d. Programming: Open Issues
e. Documentation: Closed Issues
e. Documentation: Open Issues
f. Quality Assurance: Closed Issues
f. Quality Assurance: Open Issues
LIVE ERROR/911 Fixes

Topic: Close messages

Ability to flag a message as closed and be able to sort message lists using this extra indication. Messages are sometimes more powerful than todo’s and are used as todo areas.

Archive of messages would also be helpful, this complements closed.

The message list could then be based on these simple filters open, close and archived.

regards,
S.

Topic: finer grained permissions

We are adding two projects per project too, one for contractor facing, and one for client facing. We have to download documents, or copy/paste back and forth between the projects. We basically don’t want contractors seeing all the material on the clients site, and and the other way around, but they do share some material.

Apart from a more indepth autorization system, one thing that would be nice for us would be to have the ability to copy documents and files from one project to another. So a contractor posts a file ready for the client, and we just send it to the client project instead of download, switch project, upload.

Another idea I had would be to have tabs with permissions per tab, so there would be a Contrator tab in a project with one company having access and Clent tab with a different company having access. Maybe this is just done on the message board. Right now I put private links in all the message boards linking client to contrator sites. Bit of a hack, but it’s faster than going back to the dashboard.

Topic: finer grained permissions

We also have multiple “Company’s” in projects and it would be nice to be able to select them individually for “Privacy”. We are in the same boat with Clients vs. Contractors/Subcontractors.

Topic: finer grained permissions

I echo this.

I want everyone to be able to read/write, but no one be able to edit or delete.
I want to use it as a permanent archive of the conversation that goes on with clients, including agreements and change orders that are made.

Topic: finer grained permissions

This would be the single most useful feature for our organization. We are a consulting firm working with clients and other subcontractors. We do not want our subcontractors to have access to specific client data. I would like to give access to view certain milestones, tasks and files to specific people or groups of people. Currently the only way I can do this is if I create multiple projects, one or the client and one for subcontractors.

Topic: finer grained permissions

I would also like a more fine grained permission system implemented.

I work with other freelance employees on my contracts and I would like the ability for them to have “read only access” to Writeboards, To-Dos and Milestones and I don’t want them to be able to view messages at all. Currently this is not possible and I have to create two projects which makes management a pain. I might have to move to another system if this feature isn’t implemented.

Is there a way we can make a more formal request?

Topic: finer grained permissions

I am in the same boat and having this would prevent all the little workarounds we have come up with. I really hope they put this in the the ‘treetop’ addon. ;)

Topic: finer grained permissions

We would like to be able to specify who can access documents on a document category or document basis vs. just on a project level. For example, we would like to upload contractual documents that only PMs and administrators can access, but still have other documents that team members and clients can see. The only options I see to do this are to a) create separate projects for the private documents or b) make the document category private. Option a works but is a little cumbersome and option b only allows one person to see the document.