- Display a dialog when the user approves an image
- Changing A Mockup URL Slug
- Extending Backbone Models, Views and Collections
- Adding Custom Scripts and Styles
- ph_website_publish_thread
- New Comment Threads
- Add additional notification emails
- Display a welcome message for new users on mockup projects
- Change the subscribed user email based on a role
- How to Install SureFeedback & Addons
- Updates
- Should I install this on my own site or a dedicated installation or subdomain?
- Caching and SureFeedback
- Dashboard Shortcode
- Adding A Project Shortcode To Your Site 3.1.x and lower
- Project Shortcode
- Hosting
- Cloudways Compatibility
- How to Activate your SureFeedback and Addons License?
- Adding a Subscribed Projects Shortcode 3.1.x and lower
- Customization
- Emails
- Permissions Cheatsheet
- How to Integrate SureFeedback with Slack
- How to Export Comments in PDF/CSV file?
- Known Issues
- Increasing the WordPress Memory Limit
- WPEngine Cache Exclusion
- Litespeed Caching
- Emails Not Sending
- Flywheel Compatibility
- Debugging
- Varnish Caching
- Gridpane Compatibility
- Session Expired Notice in Chrome Incognito
- Breeze Compatibility
- W3 Total Cache Compatibility
- Website Comments Not working
- Swift Performance Caching
- Flywheel Cache Exclusion for Project Access Links
- WPRocket Compatiblity
- How to enable a different site for my license
- How to generate an invoice for my purchase?
- Download Failed: Unauthorized
- How do I translate SureFeedback into my language?
- Creating Client and Colleague Accounts
- How to give a person access to a project?
- How to use SureFeedback on any external site
- How to Use SureFeedback with WPML to Collaborate on Multilingual Sites
How to give a person access to a project?
Giving Project Access
By default, visitors, Project Clients, and Project Collaborators won’t have access to any projects on your site. There are several ways to give a client access to your project. You can find the individual project access settings for each mockup or website by visiting the Edit Mockup or Edit Website page. There are several access options for each project, as seen in the screenshots below and each is explained further down the page.
![](https://surefeedback.com/wp-content/uploads/2023/08/file-ehMRuvaQoI-1024x597.png)
Also, be sure to check out the Permissions Cheatsheet article to make sure you’ve assigned a role with the access level needed to collaborate on the project.
OPTIONS FOR GIVING A PERSON ACCESS TO A PROJECT:
- Require Users to Login/Must be logged in
- Anyone with the Project Access Link
- Anyone who visits the project/site
A. Require users to login / must be logged in
A visitor must be logged into the site where SureFeedback is installed in order to see and comment on the project. If a visitor visits through the access link, they will be prompted to login to view the project. If you choose this option, you may want to create accounts for your clients ahead of time under Users > Add New. Then give them access by adding them to the Project Members meta box on the right side of the project page.
![](https://surefeedback.com/wp-content/uploads/2023/08/file-h2ytLUoeIY.png)
B. Anyone with the Project Access Link
A visitor must follow a project access link to see and comment on the project. They do not need an account and do not need to be logged in. If a visitor visits through the access link, they can see and leave comments on the project. When they leave their first comment, they will be prompted for a name, email and password. This self-registers the user with a Project Client role and logs them into the background.
You can find the project access link under the project title on the Edit Mockup or Edit Website page.
![](https://surefeedback.com/wp-content/uploads/2023/08/file-plP2bEPury-1024x169.png)
C Anyone who visits the project / site
Anyone who visits the mockup project or website can see the project and make project actions. They do not need an account and do not need to be logged in. When they leave their first comment, they will be prompted for a name, email and password. This self-registers the user with a Project Client role and logs them into the background.
We don't respond to the article feedback, we use it to improve our support content.