Internal app catalog, request build, ticketing, and mini roadmap per workspace.
Core features
From catalog to ticketing, Apps keeps custom needs organized.
List of internal applications ready to use or activate.
Submit new application needs with brief and business objectives.
Monitor build progress, changes, and fixes in a structured way.
Feature priorities and timelines tailored to each team's needs.
Collaboration notes and attachments for organized briefing.
Support levels and SLA prepared for enterprise needs.
How it works
Submit new application or feature request.
Team defines scope and estimation.
Build executed per priority.
Delivery and handoff to user team.
Ongoing iteration via ticketing.
Use cases
Process & security
Apps ensures clear milestones, tracked changes, and controlled access.
Each project has milestones for clear and measurable progress.
Scope changes are logged to avoid impacting main timeline.
Access follows roles and workspace when connected to Core OS.
Brief, decisions, and updates are stored for easy audit.
FAQ
Apps focus on custom app requests and ticketing, not standard modules.
Team submits a brief, then scope and estimation are agreed before build.
Limits follow subscription plan and workspace priority.
Yes, changes become tickets for the next iteration.
SLA and support tiers are prepared incrementally for certain plans.
Access follows roles and workspace through Core OS.
Yes, Arena Commission can use Apps as a request channel.
Related modules
Foundation for accounts, workspace, and billing across all modules.
Wallet and billing for subscriptions and invoices.
Commission mini-game and custom requests.
Work templates and document automation for operations.
Start small and continue iteration via ticketing.
