Users
Name the team that will use the application and the actions it may already perform.
Applications for your teams
Choose the tasks, access and information each team needs. Test the application with them, publish an approved version and keep the previous version available if needed.
Your requirements
Name the team that will use the application and the actions it may already perform.
Choose the tasks the team needs in warehouse, transport, commerce or support.
Describe the decision or result users need to see when they finish a task.
What is included
Shows the right pages and actions for that team.
Adds the chosen warehouse, transport, commerce or support views.
Your branding, enabled features and access settings stay with your organisation.
The application uses Ysend's existing records, so teams do not work from a separate copy.
Access and security
The application checks who is using it and which organisation they belong to.
Access to Ysend data is limited to the task and expires after a short time.
Ysend still checks permissions and business rules for every action.
Temporary access ends without leaving a reusable credential in the application.
Before publication
Combine the approved features with your organisation's settings.
Reviewers check pages, wording, permissions and errors before publication.
Keep the approval or rejection linked to the exact version reviewed.
Publication
Confirm the version shows only the intended features and data.
Record which version was approved and by whom.
The approved version becomes the application your team uses.
If something goes wrong
A problem with access, behaviour or compatibility starts a review.
Choose a version that was already reviewed and approved.
Keep a record of who changed the version, for which organisation and with what result.
Connected to Ysend
Tell us who will use the application, which tasks matter, what they may access and who approves publication. We will plan testing and a way back before building it.