Structure plugin allows users to add/be assigned to issues; even though they are not in the project.

[RukiJ]

We are evaluating Structure with host of other plugins to move from OnDemand to download version.

Scenario described below:

Projects; ABC, XYZ and KLM

User: sam is not a Admin, Dev in ABC or KLM. but only a Developer in XYZ

sam logs in.

Go to Structure board on the project XYZ, sam can add issues to ABC, and also get assigned to issues of ABC.

is this normal?

[Igor Sereda [ALM Works] · Accepted solution]

Structure permissions are configurable by the admin / structure owner. You can open menu Structure | Manage Structure, and then click Configure to change the permissions for a given structure - see here for details: https://wiki.almworks.com/x/QIBp

Also, a structure does not inherently belong to a project. It is a separate notion, very flexible. For example, you can have separate structures for the projects you mentioned:

1. Create structures named ABC Structure, XYZ Structure, KLM Structure.
2. Assign corresponding permissions - for example, for ABC Structure, use the following rules: (I) View for Users of project ABC; (II) Edit for Developers of project ABC.
3. Make each Structure default for its project. Open Administration | Projects, select project ABC, click Structure (the administration screen) and select "ABC Structure" as the default.
4. Turn ON auto-switch on the project pages: open menu Administration | Structure | Defaults, scroll down to "Structure User Interface Defaults", and make sure "Auto-switch (project/component...)" is turned ON, click Change if needed.

Now, if you open Structure panel on the project page, it will automatically switch to show the structure related to that project, and only the developers in that project will be able to modify the structure.

Igor