Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just created a Ubuntu development server and I would like to work with two teams on it. I want people from these teams to do anything they want, but I don't want them to be able to see the files from the other team, how do I do that?

If I put them in the sudo-ers file, they can access the folder from the other team, without sudo, they complaint that they aren't able to install new software on the machine. How can I give them the power they need without the ability to see the other team's files?

share|improve this question
Don't give them sudo rights. What you want is giving someone a key without giving them a key. – mailq Sep 29 '11 at 22:08
Giving them the right to do absolutely everything except one thing is a strategy that's doomed to fail. Instead, you need to give them the right to do everything they need to do and nothing more. – Skyhawk Sep 30 '11 at 2:48

How about two different virtual machines, that way they each can do what they want to the system without having access to each others' files.

share|improve this answer

You can give access to sudo on a per command basis.

add apt-get, starting and stopping needed daemons in /etc/init.d and that's it.

share|improve this answer
Sounds like exactly what the doctor ordered. may be a useful tutorial to accomplish this. – Skyhawk Sep 29 '11 at 23:24

Create two groups, and add users to each group based on the team separation.

Also, I'd create two home dirs (e.g. /home/team1 and /home/team2) and when creating users create their home dirs under each, as well as setting them to the correct group

useradd -D /home/team1/jsmith -g team1

Then implement @Hubert suggestion of restricting the 'sudo' activities. Sudo has tons of different configs it may take several back and forths with the teams to square them away.

share|improve this answer
Don't forget umask and /home/{team1,team2} permissions. – grs Sep 30 '11 at 1:33

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.