Forum: Transit support
Topic: Restrict Transit user access to projects/restrict projects displayed in 'Project brower' per user
Poster: Steveling2
Post title: User scope works (with limitations) for new projects
Hi Oiseau noir,
Thanks for your reply. Setting the user scope in a new project does hide the project from other users, but you cannot define the User, i.e. the User field is preset to my user and is uneditable. This means such a project is also hidden from a checker, for example, and you can't 'assign' a project to another user, only to yourself.
I've played around a bit with this, but I don't think there is a functionality that will do what we want. To be fair though, the company has been happily using Transit for years without such functionality, so it's not a big problem.
Steveling2
Topic: Restrict Transit user access to projects/restrict projects displayed in 'Project brower' per user
Poster: Steveling2
Post title: User scope works (with limitations) for new projects
Hi Oiseau noir,
Thanks for your reply. Setting the user scope in a new project does hide the project from other users, but you cannot define the User, i.e. the User field is preset to my user and is uneditable. This means such a project is also hidden from a checker, for example, and you can't 'assign' a project to another user, only to yourself.
I've played around a bit with this, but I don't think there is a functionality that will do what we want. To be fair though, the company has been happily using Transit for years without such functionality, so it's not a big problem.
Steveling2