How can we restrict developers to editing objects within specific applications in Appian Cloud?
We are building a single Appian system, but we plan to divide it into multiple applications based on responsibilities and business domains.
For example:
・Application A
・Application B
・Business Common Application
・Common Components Application
・Administration Application
Our environment is Appian Cloud, not an on-premises installation.
Multiple development teams and vendors will work in the same Appian development environment.
To prevent developers from unintentionally modifying objects owned by another team, we would like to control which applications each developer account is allowed to develop.
Our expected behavior is:
・Developers assigned to Application A can create and modify objects belonging to Application A.
・They can reference shared objects from the Common Application when necessary.
・They cannot modify objects belonging to Application B or other applications.
・Developers assigned to Application B should have the same restrictions for Application B.
・System administrators may modify all applications and objects.
We are considering creating separate developer groups for each application and configuring application and object security.
Could you please advise on the recommended approach for implementing this type of design-time access control in Appian Cloud?
In particular, we would like to confirm the following:
1. Can developer permissions be controlled at the application level?
2. Does application security automatically apply to all objects contained in the application?
3. If not, must security be configured individually for each Appian object, such as Interfaces, Process Models, Record Types, and Expression Rules?
4. How should security be managed for shared objects that need to be referenced by multiple applications but modified only by the common development team?
5. Is there a recommended group and security structure for a multi-team or multi-vendor development environment?
6. Are there any limitations where a developer can still modify an object through another application or by directly opening the object?
7. What is the recommended way to prevent accidental cross-application modifications?
We understand that an Appian object may be included in multiple applications. Therefore, we would also like to know whether security should be enforced based on individual object security rather than application membership.
Our main objective is not runtime access control for end users. We want to restrict design-time development access for developer accounts and clearly separate ownership and modification responsibilities for Appian objects between development teams.