# Key Features Stacker is made up of pages of your data. The pages can be edited with simple drag and drop to best display your data to your users. ## Fine tune each table Each table has settings to allow you to configure exactly which records appear in Stacker and exactly which fields. You can also pick which field should be the display name of the record, and set a default field value. ### Control navigation Display navigation as a side or top view, easily arrange each item with easy drag and drop. Choose to apply user roles to your navigation items and add in icons. ### Flexible permissions You can use [permission rules](https://docs.stackerhq.com/stacker-classic/permissions-and-security) to configure access to data with fine grained controls down to the individual field. Then taking this one step further with [advanced Permissions](https://docs.stackerhq.com/stacker-classic/permissions-and-security/configure-a-permission-rule/table-permissions/multiple-permission-rules) you can have multiple different [user roles ](https://docs.stackerhq.com/stacker-classic/permissions-and-security/set-up-user-roles)in the same app. ### Make it yours Brand your workspace and each app with your color, logo and icon. ### Create multiple apps Got more than one app to build? No problem, you can create multiple apps in a single workspace. {% hint style="info" %} Need some extra help building? Reach out to the Stacker community [here](https://community.stackerhq.com/). {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.stackerhq.com/stacker-classic/getting-started-quick-guide/key-features.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.