Is it possible to differentiate access between components?

Question

JIRA

Hello.
Several departments are working on the project: designers, managers, developers, etc. It is clear that it makes no sense for developers to get involved in the tasks of managers, and for designers - in the tasks of developers, etc. Created several components responsible for different departments (administration, web part, marketing, design, etc.). How now to differentiate access? So that most users only sit inside their component? Or is this the wrong way and should be done differently? Before that, they used a different project management system - it was set up quite simply there.

Answer 1

It is clear that it makes no sense for developers to get involved in the tasks of managers, and for designers - in the tasks of developers, etc.

It may very well make sense if, for example, the frontend task is blocked by the backend, and the front wants to know how it is with the status, etc.
It doesn’t make much sense when a designer opens his own dashboard, and it doesn’t differ in any way from the one that a marketer or key account manager sees.
Components can be seen - "differentiation" of access at the level of dashboards.
Components should not be visible - the distinction is at the project level.
PS: Components can be visible, but individual task comments in these components should be hidden. For example, if the client has the right to see tasks, but should not see individual comments.
This situation is resolved right for each comment.