View this page in the latest version of Appian. Plan View Share Share via LinkedIn Reddit Email Copy Link Print On This Page This page describes the view's benefits, elements, access requirements, and security. Access the Plan view To access the Plan view, open your application in Appian Designer, then click Plan in the navigation pane. Caution: The Plan view does not prevent multiple people from editing at the same time. Coordinate with your team to avoid overwriting each other's changes. All updates are automatically saved. Purpose The Plan view is where you use Appian Composer to design and organize an application plan before building it. Business users, developers, and subject matter experts can collaborate in real time to align on requirements, personas, processes, and screens. From there, Composer carries the plan into development. Composer creates and modifies design objects through natural language, working through the plan one user story at a time. Where the Plan view is where you establish what to build, the Build view is where Composer builds it. Plan view benefits The Plan view provides the following benefits: AI-driven assistance: Composer helps you generate and refine application requirements, define personas, and model your data by suggesting enhancements and translating business needs into Appian concepts. Faster development: The Plan view gives developers a clear starting point. Composer can generate starter design objects from the application plan, reducing setup time and helping developers move from planning to building. Visual clarity: The Plan view provides a structured view of your application's requirements, helping you see how each part fits together and refine ideas before development begins. Unified collaboration: Developers, business users, and subject matter experts can work together using a shared, interactive plan to stay aligned on application capabilities and design. Centralized resource: The Plan view keeps requirements, personas, processes, screens, business rules, and the data model in one shared application plan. This shared resource helps new team members get up to speed and helps the team maintain a consistent understanding of the application's purpose. Easy access to Process HQ: Composer automatically adds a Reports and Dashboards Library page with content filters to generated sites, so users can access Process HQ features in the application. Elements The following image highlights the elements that make up this view: Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close # Element Available actions 1 Header bar Learn more about the header bar. 2 Navigation pane Learn more about the navigation pane. 3 Tabs UX PreviewStoriesPersonasProcessBusiness RulesData Model 4 Workspace Review and refine the selected part of the application plan. Use START BUILDING to generate design objects and continue in the Build view. 5 Composer chat panel Use Composer to generate and refine the application plan. Requirements to access the Plan view The Plan view has the following access requirements: Appian Designer access: You must have access to Appian Designer. Business users must be added to the Designers System Group. Supported region: You must use Appian Composer in a supported region. Access may be limited unless cross-region configuration is enabled or you use inference profiles. Security The Plan tab in Appian Designer is available to anyone with access to the application. See Requirements to access the Plan view for access prerequisites. Your available actions in the Plan view depend on your permission level in the application's security role map. The following table lists the actions available for each permission level. Action Administrator Viewer View Plan view tabs Yes Yes Manage Plan view content Yes No Use START BUILDING Yes No Generate design objects* Yes No * To generate Create, Update, or Delete actions for a record type, you must also belong to the Process Model Creator group. Feedback Was this page helpful? SHARE FEEDBACK Loading...