- Install SureFeedback & Addons
- Update SureFeedback
- Translate SureFeedback
- WPML For Multilingual Sites
- Main Site Or Dedicated Installation?
- Automating SureFeedback Workflows With OttoKit
- Manage Licenses
- Caching & SureFeedback
- Litespeed Caching
- Chrome Incognito: Session Expired Notice
- Gridpane Compatibility
- Breeze Compatibility
- W3 Total Cache Compatibility
- Download Failed: Unauthorized
- Flywheel Cache Exclusion
- Generate Invoice
- WPRocket Compatiblity
- Swift Performance Caching
- Debugging
- Varnish Caching
- Website Comments Not working
- Flywheel Compatibility
- Emails Not Sending
- WPEngine Cache Exclusion
- Increasing WordPress Memory Limit
- Client & Colleague Accounts
- Permissions Cheatsheet
- Slack Integration
- Export Comments in PDF / CSV
- Provide Project Access
- Hosting
- Subscribed Projects Shortcode (Below 3.1.x)
- Activate SureFeedback License
- Dashboard Shortcode
- Cloudways Compatibility
- Known Issues
- SureFeedback On External Site
- Emails
- Project Shortcode
- Customization Settings
- Project Shortcode (Below 3.1.x)
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.

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.

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.

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.