Define what a service includes, what information employees must provide, who owns delivery, and whether authorization is needed. Keep those definitions connected to the requests they produce.
Explore with sample data. Adapt fields, views, and workflows for your team.
Describe the outcome in language an employee understands. Include prerequisites and who can request it; do not use internal department codes as the service name.
Published offerings can be selected in the request form. Confirm the owner, reviewer, and request requirements before changing the catalog state.
Remove the offering from new selection while preserving linked requests. Submission also checks current availability, so an outdated selection is not enough to create a valid request.
The catalog describes eligibility; it is not, by itself, an access-control policy or an account-provisioning engine. Configure member permissions for restricted services and keep technical fulfillment in the authorized system.
“Equipment setup” should tell employees whether the service includes a laptop, charger, dock, and collection appointment. State where it is available, the required notice, and who answers questions. A clear offering prevents employees from interpreting a short catalog label as an unlimited commitment.
Stop accepting new requests when a service is no longer available. Review requests already in progress with their owners: finish the agreed delivery or communicate a replacement offering. Keep the original request and authorization so a later policy change does not make the earlier decision impossible to understand.
No. A useful service definition explains the deliverable, required information, owner, target, and authorization policy. The request form collects one employee’s need against that definition.
Yes. The example uses service-specific fields for supplies, equipment, and system access. Employees do not need to fill equipment details for a stationery request.
The request selector lists published offerings, and submission checks current availability. Retired service records remain useful for understanding earlier requests.
Do not assume so. Selected context is retained on the request. A service owner should decide how changed terms affect open work and communicate any revised commitment.
Use Jodoo’s member and record permissions and test the installed access policy. The catalog’s eligibility text explains the rule to readers, but descriptive text alone does not enforce it.
Make each offering understandable, assign its owner, and test its request path before expanding the catalog.
