Skip to main content
All CollectionsGetting Started
No-Account Collaboration
No-Account Collaboration

Collaborate in verybusy.io without creating and account

Emily Fishman avatar
Written by Emily Fishman
Updated over a week ago

To streamline collaboration and feedback on your projects, verybusy.io has launched a no-account collaboration feature. This option allows project owners to quickly share their work with clients and stakeholders through a public share link, bypassing the need for account creation.

What is No-Account Collaboration?

This feature, accessible through the "Share Project" modal, enables you to generate a public share link. Clients and stakeholders can use this link to collaborate within your project as a guests — leaving comments, adding labels to images, and contributing assets—without needing a full verybusy.io account.

verybusy.io no account collaboration share link for retouching projects

Who Can Use This Feature?

No-account collaboration is designed for project owners and collaborators who have full accounts with verybusy.io. It offers a convenient way to involve clients and other external reviewers in your projects.

Why Implement This Feature?

Our goal is to tailor the verybusy.io experience to the specific needs of our users. No-account collaboration minimizes barriers, enabling quicker and more effective feedback. The only emails sent to users accessing the project through this method (guest users) are essential project notifications.

When to Use No-Account Collaboration?

Use this feature when:

  1. It's permissible to generate a public link.

  2. Quick client access is needed without the hassle of account registration.

What Information Is Required from Users?

Upon leaving their first comment/markup, users will be prompted to provide their email address and full name. This information helps maintain transparency about who is providing feedback and allows us to send them relevant project updates.

This information is only needed to be entered once, verybusy.io will remember the guest user when they return to the project or access another verybusy.io project's share link.

What Are the Limitations?

Users accessing projects via a public link cannot:

  • View a dashboard of all their projects (projects must be accessed through the same project share link each time).

  • Customize notification settings.

  • Invite new collaborators or create new projects.

However, they can share the public share link with others. If further collaboration features are required, we recommend inviting the individual as a Project Collaborator. This invitation requires the collaborator to sign up for a full account, granting them access to a comprehensive project dashboard and additional account settings.

Security

Like any public share link, there's a risk that unauthorized users might access it. Our share links are designed to be secure and virtually unguessable. However, the safety of your project depends significantly on how these links are distributed. Always send project share links directly to specific, intended recipients and avoid making them publicly accessible.

For heightened security, opt to invite your clients and other collaborators via the "Invite Collaborator" email option in the "Share Project" modal. This method requires collaborators to register or log in to a verified verybusy.io account, ensuring secure and authorized access.

verybusy.io no account collaboration guest information

How to Disable a Project Share Link

Should you need to deactivate a public share link, simply choose the "Only Invited Collaborators Can Access" option from the share link dropdown menu in the "Share Project" modal. This setting immediately disables the share link, blocking access to anyone who hasn't already used it to enter the project.

Conclusion

No-account collaboration simplifies the process of sharing and reviewing projects on verybusy.io, making it easier to receive valuable input without the need for account creation. For full functionality and a more integrated experience, consider upgrading invited users to full project collaborators.

Did this answer your question?