Overview
Application Preferences are team-level defaults that guide internal app planning. They help AlphaTales keep internal app recommendations aligned with how your organization wants to build.
For team workspaces, preferences are part of getting ready to build internal apps.
Who Can Manage Preferences
Owners and admins manage Application Preferences for the team. If you are a member or viewer and the preferences are incomplete, ask an owner or admin to update them.
Use team roles carefully. Preferences affect the default direction for internal app planning across the workspace.
Review Technology Preferences
Technology preferences capture the team's preferred technical direction. These choices help AlphaTales avoid recommending a build approach that does not fit your team's standards.
Keep preferences current when your team changes its preferred stack or delivery approach.
Review Design Preferences
Design preferences guide the expected look, feel, and interaction style of internal apps. Use them to keep generated planning aligned with the team's product and brand expectations.
Keep this practical. Internal tools should be clear, efficient, and easy for repeat users.
Review App Defaults
App defaults describe common expectations for internal app behavior. They can shape how AlphaTales thinks about forms, dashboards, permissions, reporting, and operational workflows.
These defaults reduce repeated setup work across internal projects.
Review Integrations
Integration preferences capture the tools and systems your team commonly connects to. This is especially important for internal apps that depend on existing data, reporting, approvals, or operations.
Tip: Complete integration preferences before planning a data-heavy internal app. It helps the project describe real system dependencies earlier.
Next Steps
After Application Preferences are complete, create an internal app project and follow the Internal App Journey from Project Breakdown to Dev Pack.