Give Access To A Single Project

[affinityjeff]

Is there a way to permission a user so they can only see a single project? We want to give our customers visibility into their project, but no other projects. I tried creating a Guest user, denying access to all modules and then giving access to only a single project, but the login still shows all projects.

Thanks for any advice :)

Version 2.0.4

[pedroa]

create a role without permissions.
give that role to the client.
on his permissions tab, add permission to view his company only.
on his permissions tab, add permission to view the project only.

Pedro A.

[sandclock]

Hi
I want to do same but when i try to create new user it gives me option of administrator ceo etc how do i add user type "client" to it?
Thanks for help :)

[ajdonnison]

The user type is not the same as a role. It doesn't matter what type you give the user, it matters only what permissions and what roles they get. This is in the Permissions tab of the user information page.

[caseydk]

Administrator in that sense is similar to a person's job title. It doesn't actually explain their job or what they are allowed to do.

[starcem]

Pedro,

I was looking for an answer to the same question when I found your solution.

However, when I tried it (doing exactly as you suggested), and log in as the client, I see no projects at all. Is there anything else I should do?

Regards
starcem

[pedroa]

Did you follow the indications correctly? please post here the role permissions contents and the direct user permissions.

By the way have you checked if the combo filter on the projects list is set to "All"?

Pedro A.

[starcem]

Hi Pedro,

I set up a brand new role and did not give the role any permissions. I've checked that and it's still the case.

I set the client up with this role (and only this role).

In the client permissions, I then selected as follows:

Module: Projects
Item: The specific project that I want him to access
Access combo: Allow
Access checked
View checked
Edit checked
Delete checked.

By the combo filter on the projects list, I would believe that you mean the item which initially has all as the default. I would expect that I couldn't leave it at all as this is where I have specified the project.

Mick (starcem)

[pedroa]

Cool and what about....


on his permissions tab, add permission to view his company only.


?

(BTW: you don't need the edit,add,delete on the project just the view.
Also if you need to see the top Projects menu, just add the permission to access the Projects module)

Pedro A.

[starcem]

Pedro,

Once I give access to the company, he gets to see all of the projects for that company.

I've tried a number of combinations of things (i.e. projects access/specific project, company/projects/specific project, etc), all to no avail.

Mick (starcem)

[Karen]

http://docs.dotproject.net/tiki-index.php?page=2.0+Permissions+Examples

Try the one that restricts to projects - you set the Item level within the user setup. User Admin > Select the User > Permissions tab

[starcem]

Hi Karen/Pedro,

Finally got it going.

What I eventually did was as follows:

No permissions fot the role.

User permissions:

Module: Companies
Item: Selected company
Access: Access, View

Module: projects
Item: all
Access: Access

Module: Projects
Item: Selected project
Access: Access, View

Project menu appears. On clicking, the selected project appears. All the tabs above still indicate the number of projects in the system but that's fine as the only one actually shown is the selected one.

Thank you both for your help.

Mick

[starcem]

Karen/Pedro,

Just one other things I then had to do add is the following:

Module: Tasks
Access: Access, View

This then enabled the client to work with the tasks related to that project.

Mick

[pedroa]

That's exactly what I said!
There are times I think I am talking to the fish...
Clear your mind and read slowly next time please, my first post said it all...

Pedro A.

[starcem]

Hey Pedro,

I don't want to rock the boat, but it isn't what you said. In the original post that you refer to, you had left out the access to the Projects module before giving access to the specific project.

Furthermore, I have found that I got jumped too early at the solution. Whilst giving access to the Tasks allows view of the tasks, the client can't add/edit tasks.

I'll play around with this further and when/if I find a solution, I'll post it for completness sake.

Mick

[starcem]

Okay,

These are the permissions I had to set to give a client full access to the one project.

Role permissions:

None

User permissions:

Module: Companies
Item: Selected company
Access: Access, View

Module: Projects
Item: all
Access: Access

Module: Projects
Item: Selected project
Access: Access, View, Edit

Module: Tasks
Item: all
Access: Access, View, Edit, Delete

Cheers

[DotVince]

Hey Pedro,
I don't want to rock the boat, but it isn't what you said. In the original post that you refer to, you had left out the access to the Projects module before giving access to the specific project.

Mick

As far as I know, you MUST select access to the Projects module before giving access to the specific project. :confused:

Hence initial reply by Pedro was correct.

- Vince

[starcem]

Vince,

I do beg to differ. You may have known to read between the lines, but I was asking as a new user. I took Pedro's instructions literally. They didn't work. If you have a look at the post, there is definitely no mention of giving access to the projects module.

Anyway, it doesn't matter now because I've got it working and documented what I had to do.

Mick

[DotVince]

Hi Mick,
You may be right, in that I did 'read between the lines' due to having already gone through the pain of learning a little (very little - no expert) about the DP permissions.

Another post that may is by Casey here:
http://caseysoftware.com/dotproject-permissions

Best wishes,

- Vince

[caseydk]

That's one of my more popular posts... and that's why I spell it out so explicitly in order to head off misunderstandings, etc.

[adrianhedley]

I am looking for a way to give access to projects created by that particular user.

this means that user1 will be given permissions to create unlimited projects but can only access, view, edit the projects he created. Projects created by other users need to be completely hidden from user1. Then user2 cannot view projects created by user1.

In other words only project creators can view their projects and give permissions to other users to access, view, edit that project.

is this possible with the current admin role management system?

[caseydk]

Nope. Instead you should give them each their "own Company". You can call it something different, but then base the permissions based on that.

[starcem]

In addition to everything stated in post # 16, I found that I also have had to give Access, Add, Delete, Edit and View permissions to the Task Logs, Calendar and Files modules...