Share useful reference links
Show the team existing work and examples, with enough context to explain how each link relates to your request.
What you need
- Links to your current project or examples
- Permission to share any restricted material
Select relevant examples
Choose a few links that illustrate a specific point: layout, tone, movement, functionality or the current problem. Add a short note for each, including what you like and what should be different.
Check access
Open each link and confirm it points to the intended page or file. For a document in another service, check its sharing permissions there. If access is restricted, explain how the team should request access rather than pasting account passwords.
Place links in the request
Use the links field in the service request form. Put the main requirements in the technical brief and reference your examples there. For an existing project, send the links in its conversation or email instead.
Review before sending
Check for outdated versions and broken or incomplete addresses. Include a file name or page title beside each link so it remains understandable if the destination later changes.
A reference demonstrates an idea; explain the desired result instead of assuming the team will copy everything it contains.
If it doesn't work
The team cannot open the link
Check access permissions and the exact address. If appropriate, attach a supported file or a relevant screenshot through the service request form.
Last checked: 9 September 2026
Was this helpful?
Still stuck?
Tell support which step stopped you and what you saw. Never send passwords, verification codes or full payment-card details.
Contact support