1. Architecture in brief
BeautyBlast is a CloudWinks app in the Specialist services and communities group. Each record belongs to a company, and other companies cannot see it. It builds on Crux. Its screens, fields and menus are definitions, built by the same pipeline as every other CloudWinks app.
2. Service boundary and intake
BeautyBlast owns its own records. People and companies come from Crux rather than a separate user list, files are stored in MediaMogul and linked, and work that belongs to another app opens in that app.
3. Data handled
Clients, appointments, services and product inventory.
4. Integrations and ownership
BeautyBlast uses the shared Crux record for clients and staff, so a client is one record across the platform.
5. Security and access
Sign-in, roles and permissions come from KeyKook, and people and companies come from Crux. Each record belongs to a company, and other companies cannot see it. Any record shown through another app, a portal or a combined view still passes that app’s permission check, and money, security and company-account work always runs on the server.
← More Specialist services & communities apps · All application briefs · How the framework works