Complete Website type choices
Select any applicable type: Corporate business, Service-based, Product showcase, E-commerce, Booking, Landing page, Portfolio/projects, Client portal, SaaS/software or Recruitment/careers.
Exact navigationSecure recipient link → Website Design Brief
Before you begin
- Confirm the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide covers
Select any applicable type: Corporate business, Service-based, Product showcase, E-commerce, Booking, Landing page, Portfolio/projects, Client portal, SaaS/software or Recruitment/careers. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Secure recipient link → Website Design Brief.
- Go to the relevant website brief step section containing Website type choices.
- Enter or select Website type choices using the supported value described below.
- Continue to the next step or save the current brief so autosave records the value.
- Reopen the brief or review page and confirm the value is shown correctly.
Fields, choices and supported possibilities
Website type choicesSelect any applicable type: Corporate business, Service-based, Product showcase, E-commerce, Booking, Landing page, Portfolio/projects, Client portal, SaaS/software or Recruitment/careers.
Code-backed validations and workflow rules
- The field is stored as part of the current request or intake answer set.
- Leave an optional field blank only when the form permits it; required fields must pass server-side validation.
Expected result and verification
- The complete website type choices workflow completes without a validation, permission, ownership or availability error.
- The related record, portal view, activity entry, notification log or API response shows the expected state.
- Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.
Security, privacy and operational checks
- Use controlled test records and non-production credentials before wider rollout.
- Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.
