Topic: UPDATE: Clearer admin settings

Nice update – it would be handy to click the labels for project permissions checkboxes. Basics people c’mon ;)

Thanks for a great app and service once again – kee

Topic: UPDATE: Clearer admin settings

I’m not sure that my earlier post was correctly understood.

As the account owner, I am able to assign admin privileges and have done so to two other individuals in my company. Those new admins now have the ability to assign additional admins. I don’t see how this can be considered a good thing.

My comment about sensitive information has nothing to do with billing. It has to do with project content. For example, we have a few projects that are for management eyes only (we discuss company finances, human resource matters, etc.). An ‘errant click of the mouse’, and by that I mean a true mistake, could expose that information to unintended individuals. Again, this is a clear risk (and one that I could easily see happen) that needs to be mitigated.

As mentioned by another poster, all of this could be fixed by having the account owner, and only the account owner, have the ability to grant admin access.

Topic: UPDATE: Clearer admin settings

Sure thing. The programmer who put this together is out of town until Monday, but we’ll see if we can have someone else take a look.

Topic: UPDATE: Clearer admin settings

Thanks Jason.

Topic: UPDATE: Clearer admin settings

OMG – I send an email to support , no more comments

Topic: UPDATE: Clearer admin settings

I’ve noticed that editing (and saving) a user now unchecks the admin check-box. Also, unchecking the “auto add this person to all future projects” gets automatically checked again so there’s no way to turn that off. (I’ll email this to support if it doesn’t get picked up here.)

Oh, that’s not right. We’ll have a look at that. Thanks for letting us know.

Topic: UPDATE: Clearer admin settings

I’ve noticed that editing (and saving) a user now unchecks the admin check-box. Also, unchecking the “auto add this person to all future projects” gets automatically checked again so there’s no way to turn that off. (I’ll email this to support if it doesn’t get picked up here.)

Topic: UPDATE: Clearer admin settings

We do plan on changing the way the password field words this year.

Topic: UPDATE: Clearer admin settings

I agree, I’ve mentioned this security issue before as well. The password shouldn’t be available in the source.

Topic: UPDATE: Clearer admin settings

all it takes is an errant click of the mouse by an unsuspecting admin to reveal what could be sensitive company information.

Being an admin doesn’t reveal any sensitive company information. The account owner is the only person who can see billing information and invoices. Admins only have access to the projects they’re given access to see. The account owner is the only person with access to all projects. There is no sensitive company information revealed when someone becomes an admin.

Topic: UPDATE: Clearer admin settings

I would agree with metjeff, the new admin feature is far to easy for someone to make a mistake.

I would at the very least like to see that only the Account Owner have the ability to see these checkboxes and make the change.

Topic: UPDATE: Clearer admin settings

I have to express my concern with this new Basecamp feature.

With the new way to assign admins, all it takes is an errant click of the mouse by an unsuspecting admin to reveal what could be sensitive company information. Me and the other admins in my company feel that the ability to grant admin access should be more restrictive. Not only did we like it when it was ‘hidden behind the Settings tab on the Dashboard’, we would go one step farther and say that the account owner should be the only person who can grant admin privileges to the account. Granting any admin the privilege to further assign admin rights does not represent good systems management by most definitions.

Please consider a more restrictive path to the matter of administrator privileges in Basecamp. The new way is a step backwards in our view.

Topic: UPDATE: Clearer admin settings

Thanks!

Topic: UPDATE: Clearer admin settings

Good change. thanks!

Topic: UPDATE: Clearer admin settings

Our pleasure. We know this was a confusing PITA.

Topic: UPDATE: Clearer admin settings

Thank you.

Topic: UPDATE: Clearer admin settings

One of the long standing points of confusion surrounding granting admin access in Basecamp has been where to actually grant it. It was hidden behind the Settings tab on the Dashboard. Not exactly intuitive.

Tonight we pushed an update that moves admin access to the People tab. There’s now a checkbox labeled “Administrator” under the name of each person in the main company. Check the box and the person has admin access. Uncheck it and they don’t. Just like before, only admins will see this option or be able to change it.

We certainly hope this makes granting admin access simpler. Sorry for making it so confusing all these years ;)

Topic: Can I create a 'person'?

Chancer—of course I can’t speak officially for 37Signals, but a similar question came up in a thread in the old forum about how far you could take it with regard to “re-interfacing” Basecamp. Item 4 in the TOS (http://www.basecamphq.com/terms.html) says:

Your login may only be used by one person – a single login shared by multiple people is not permitted. You may create separate logins for as many people as you’d like.

So as long as people using your custom interface are using individual logins, I think you should be okay.

On of my add-ons, www.BCTix.com , is such a re-interfacing. It exposes a different way to work with the Messages to make it easy for a client to submit new Messages in an interface that doesn’t show the other parts of Basecamp. This summer I’m rewriting it to also allow a To Do list to be “spawned” off a Message, as well as putting a few other interface bits all on one screen.

Topic: Can I create a 'person'?

As I see it, 37s won’t care if a client is using the ‘official’ interface or a third-party app, as long as they’re paying their subs. Indeed, the more ways that people can integrate Basecamp (and the other services) into their systems, the more profitable it will be for 37s. So I don’t see that limiting the API benefits them at all (quite the reverse in fact).

As Jason Fried recently indicated improvements to the API are on the way. No detail but reading between the lines, if the API moves towards a REST-style interface then it could well be that more, if not all, functions are exposed.

Topic: Dashboard bug

Benjamin, its cool.

I’m just being pedantic. If there is a thread that documents a bug, a formal response should be there. Saying that though, it would be better if we had a bug reporting area and then we can see if it is being fixed or even acknowledged, although as customers – maybe its not really the best thing. I don’t know, I suppose your right.

Topic: Dashboard bug

NickToye,

I’m sorry if my response came off as harsh. I wasn’t trying to be, so I apologize. Mostly, I think this Troubleshooting section of the forum is for things that you’re having issues in doing, but may not be related to the code within the application. Like, “I can’t figure out how to delete a company…” kind of thing. At least, that’s my take on it.

I agree that in an ideal world Jason, Jamis & crew would be keeping a close eye on all of this, but I also know that they’re busy fixing things. That being said, I’m trying to let everyone know that e-mailing support@37signals.com for critical things is the best way to go.

Again, my apologies.

Topic: Dashboard bug

The bug has been fixed, but as webbing said, existing files will still be missing the “uploaded by” text. Please email support (and include your Basecamp URL), and we’ll be happy to manually fix the files that are missing the “uploaded by” text.

Topic: Dashboard bug

Great, I’ll get down off my high horse then. :)

Topic: Dashboard bug

I believe the issue is solved but it will look ok only for the new added files.

Topic: Dashboard bug

If it is NOT their primary focus, what is the point of having a troubleshoot section? I don’t think its too much to expect to be notified within a forum thread that has highlighted an issue.

I wasn’t raising holy hell, I just felt it would have been nice to be notified here. It is quite an important bug to have been discovered, especially if you work in a team and you have no clue who uploaded the file.