Menu layouts, tables, dashboards, text aliases, custom columns, panel views and table profiles are saved at a level you choose when you save. The level determines who the customization applies to, and is the key to giving the entire organization a common standard without locking individual projects.
The four levels
Project — applies only to this one project.
Department — applies to all projects in a department.
Organization — applies to all projects in the organization.
Group — the top level, with subsidiaries and departments below it.
The most specific level wins
If a customization exists at several levels, the one closest to the project applies: project overrides department, which overrides organization, which overrides group. A customization at a higher level therefore becomes the starting point for all projects below it — unless a lower level already has its own. In that case, that one is kept.
Example: You set one standard column layout for your entire organization in AIMZ. A collaborative contract project with special reporting requirements has already created its own layout and keeps it — while the rest of the projects get the organization's standard.
Who can save at which level
To save at department, organization or group level, you must have a role with access at that level. If you only have project access, you can still customize your own project freely. Read more in What roles are there in AIMZ, and what can each role do?
Note: if you change a column name at project level, for example, it changes for all users in the project — but not in other projects you have access to. If the change should apply across projects, save it at department or organization level.
