Permissions
Assigning requests to an accountable owner
Set clear rules for request routing, named responsibility, reassignment and cover when an owner is unavailable.
Desk
Desk Governance
Looks at access control, platform costs and the risks of depending on no-code vendors.
Platform Choice
Checking export and portability before platform selection
Check records, attachments, relationships and app logic before choosing a no-code platform. See what common export routes leave behind.
Platform Choice
Checking platform limits before a wider rollout
Build a plan-specific register for records, queries, requests, workload and data delivery before inviting more users.
Platform Choice
Choosing a low-risk first no-code project
Use clear consequences, ownership, a small release and a recovery route to choose a sensible first no-code project.
Permissions
Choosing what a customer should be able to see
Choosing what a customer should be able to see: a practical guide to the key decisions and checks.
Maintenance
Keeping a history of important record changes
Choose which record changes to track, capture who changed what and why, and check the limits of native revision and audit history.
Maintenance
Keeping an inventory of internal no-code apps
Build a useful register of internal no-code apps, reconcile it with builder inventories and turn gaps into owner decisions.
Permissions
Limiting API credentials to the app's needs
Map app tasks to API permissions, distinguish user and unattended access, protect credentials and check that excess actions are denied.
Integrations
No-code app integrations
Choose between imports, one-way feeds and API actions for a no-code app, then plan data ownership, access and failure handling.
Permissions
No-code app permissions
Plan who can open a no-code app, see records, change data and maintain it. Map each grant, then check the configured data route.
Maintenance
No-code app testing
Plan practical no-code app checks for user tasks, saved data, invalid input, access and layouts before a wider rollout.
Platform Choice
No-code costs and vendor risk
Map no-code app costs across access, data, activity, plugins and maintenance, then assess the dependencies and exit effort behind the bill.
Maintenance
No-code governance
Set practical ownership, data, production review and retirement rules for internally built no-code apps.
Platform Choice
No-code platform selection
Choose a no-code platform by checking workflow fit, data sources, user access, portability and the plan needed to run your app.
Maintenance
Planning an app handover after its creator leaves
Establish app ownership, data access and connection continuity when a no-code app creator leaves.
Maintenance
Planning an exit from a no-code platform
Define what must work after a move, inventory data and app logic, inspect export limits, and rehearse a controlled cutover.
Permissions
Preventing one customer from accessing another's records
Cross-customer access is a portal failure even if it occurs only through a guessed address or export.
Maintenance
Recording defects with reproducible steps
Write useful no-code app defect reports with starting conditions, exact steps, expected and actual results, safe evidence and verification.
Permissions
Restricting records by team or customer
Define team or customer record ownership, choose an enforcement point and check access after reassignment.
Maintenance
Retiring a no-code app that duplicates a supported system
Compare real tasks, move open work and required history, cut over new submissions and retire a duplicate no-code app.
Permissions
Reviewing citizen-developed apps before production use
Use a release brief, evidence table and decision record to review staff-built apps before colleagues rely on them.
Integrations
Reviewing dependencies on paid plugins
Inventory paid plugins, trace the tasks that use them, check billing and support, and plan a safe response to an update or failure.
Permissions
Separating viewer, editor and administrator access
Define what viewers, editors and administrators may do in a no-code app, then match those duties to app and data-source permissions.
Permissions
Testing permissions with a non-administrator account
Check permitted and denied actions using an ordinary no-code app account, fictional records and the actual data route.
Permissions
Testing portal access after a customer account is closed
Closing a customer account should end the access it no longer justifies, including old sessions, shared links and downloadable files.