What’s a project? And what’s an organization?
Each organization has a user role called the Organization Administrator (or “Org Admin”), who has permissions to configure Aconex for their organization. They are responsible for creating user accounts and managing the permissions for users within their organization. Whoever registers an organization in Aconex becomes the Org Admin by default.
The organization that sets up a project within Aconex is called the project-owning organization. On written request, Oracle can assign the role and its responsibilities to an alternative organization, for example; from the Developer to the Contractor.
Who looks after projects?
Project Administrator(s), working for the Aconex project-owning organization, have permissions that let them manage project-wide settings that affect everyone working on that project (all users in all organizations). Examples: Project invitation method, and Mail attributes. They are also responsible for configuring the Mail and Document types that can be used by each organization on the project. Find your Aconex Project Admin.
Each organization also has Project Administrator(s), who are able to manage project-specific settings that affect their organization only. Examples: Auto registration of workflow transmittals and Dynamic stamp disclaimer text.
How organizations work on projects
That said, users can override some organizational and project settings, for example, when it comes to creating mail signatures for project mail. An Organization Administrator may create an organization-specific mail signature, that applies when any user in their organization sends a mail. However, a user in that same organization can choose to create their own individual mail signature, which will be applied when they send mail.