In this article, we will take a deep dive into everything concerning project creation and management, as well as some FAQs.

Table of contents

1. What is a project?
2. Adding a project
3. Project integrations
4. Project settings
5. Exporting a project
6. Archiving a project
7. Permanently delete a project
8. FAQ

What is a project?

In Feedbucket, a project is where you will manage the entire feedback of a specific website or design. Since you will likely have multiple websites or designs, it's convenient to have a separate project for each of them. A feedback submitted into a specific project will of course be tied to that project, but not only that; every project can have different settings and integrations installed. We will take a deeper look into all of that shortly.

Adding a project

We will now take a look into all of the steps required to successfully create a project.

The first thing you will want to do is to head over to the Projects section at the top of your screen, and then to click on the Create New Project button in the upper right (you can check the screenshot below to see where it is, along with all of the sections required to create a project).

1. First, select the project type, and you will see that there are two options here:

• Website - The most common project type, for whenever you want to gather feedback on a website.
• Design - When you want to gather feedback on images, for example during the early stages of website design. Please have a look here if you want to know more about this project type.

2. Then, enter the project name.

3. Enter the URL of your website (this is of course only valid for the Website project type).

4. Click on Create Project.

5. You will be automatically directed to the Installation section (for website projects).

Project integrations

One of the most powerful features of Feedbucket is to integrate it with many project management tools. We believe that most Web Agencies will already rely on one of these tools, so we have created 15+ 2-way integrations so your team can manage feedback without ever leaving their PM tool.

Let's see now how to connect an integration (or more) to your specific Feedbucket project:

1. On your project, click on the Integrations tab.
2. Click on Connect next to the integration that you wish to sync with Feedbucket.

3. The connection will be made automatically, and a window will pop up, requesting you to select the integration Workspace and Project, and where your feedback will be placed when it's created and resolved. Since integrations can have some different setups, please visit our Integrations category to find the relevant article for the integration that you wish to connect.

Do I need to use a project management tool?

This is of course not required, as feedback can be entirely managed within Feedbucket Admin. However, if your team already uses one of the supported PM tools, an integration with Feedbucket is strongly recommended. This will ensure that your team does not need to ever leave the platform they are using to manage feedback. Please head over here for the comprehensive list of available integrations.

Project settings

Now we will take a look at project settings, which can be reached by clicking on your project, and then Settings (see the screenshot below for reference). This section will allow you to manage many aspects concerning your project, like notifications, tags, Feedbucket widget behavior, etc.

Let's now take a look at what each section controls for your project:

1. General - This is where you manage the basic information of your project, and where you can archive or delete it. It's divided into:

• Settings: This lets you further edit your Project Name, Project URL and Project Image. This can be done as many times as you want.
• Danger: This indicates an area where you can make changes to your project that will prevent you from using it (temporary for the archiving, permanently for deleting). Check this paragraph for more information on archiving, and this one for deleting.

2. Widget - Everything related to the customization of your Feedbucket widget such as design, visibility, screenshot generation and client/member functionality:

• Visibility: Here you can choose who can see the widget. You will see that toggling one option will deactivate the others, as you can only show the widget to one set of users. This section also includes the query parameter option, about which you can find more information here.
• Client Functionality: This lets you fine tune the behavior of the widget for your clients only, so users visiting your website who do not have a Feedbucket account. You will see that you can toggle aspects like visibility, feedback submission, and individual features of the widget. Every change made here will also be applied to Member Functionality, as further explained in this paragraph.
• Member Functionality: This lets you fine tune the behavior of the widget for your members only, i.e. team members who have a Feedbucket account and whom you have invited to your team. You will see that you can toggle aspects like visibility, feedback submission, and individual features of the widget. Every change made here will break the sync with Client Functionality, as further explained in this paragraph.
• Screenshot: These are settings to help you if you have trouble generating screenshots, for example if the screenshot is broken or blank, usually due to the fact that Feedbucket cannot access your CSS because of certain restrictions. It includes the Basic Auth option, which is further explained here.
• Design & Presentation: This is what really lets you customize the Feedbucket widget to reflect your brand identity. You will need to first create a theme, and then apply it in this section. You can find all the details on how to create a customized theme in this article. You can also choose whether to place the Feedbucket widget on the right or left of your website, change pin colors, change the language, and change several placeholders for the widget appearance and onboarding.

3. Notifications - This is where you can set notifications for your clients, as they will have to enter their email address when they leave their first piece of feedback on the project:

• Client notifications: You can toggle whether they receive notifications for new comments, or when feedback is resolved.
• Member notifications: You will find a redirect to your own account notification settings (general, not project tied, and for feedback you have either created or interacted with).

4. Tags - Here you can add, delete, and change the order of your project tags:

• Project tags: Create tags from here. If you have integrated the project with a PM tool and it can sync tags, you will see a selection after clicking on Add tag that lets you select whether to create a Feedbucket native tag, or a tag synced with the PM tool. The main difference here is that a native tag cannot sync to any integration and stays within Feedbucket, while integration tags have a 2-way sync with Feedbucket. Read more about tags and integration sync on this article.

5. Integrations - This will allow you to make changes to all PM tools integrated into the specific project:

• Project Integrations: you can set the prefix here, meaning that when a new feedback is created, the prefix will appear on the task title of your integrations. This prefix will only appear in the integrations and not in Feedbucket.

Client/Member Functionality inheritance and override

It's important to understand the difference between the two groups of users and why we have potentially different settings in place for them:

• Client: Anyone visiting the website where the widget is installed who does not have an account in Feedbucket and is not part of your team. This can be your clients and anonymous visitors. Once they submit feedback, they will be asked for their name and email address, and will fall into this Client category.
• Member: This is someone with a Feedbucket account and that is part of your team; it can be an employee of the agency staff or a developer. They will be recognized in the website through a cookie if they are logged into Feedbucket Admin.

You might therefore want the widget to behave differently depending on the set of users, and this is entirely possible. There are cases where you may want to have your widget visible to everyone, but close the feedback submission only for clients, so your team has time to review the existing feedback before moving to the next round. That being said, it's important to understand that the Functionality settings have an inheritance and override system to fine tune widget behavior, and this will be explained next.

Client to Member inheritance

This is the default behavior: you will notice that every change made to the Client Functionality toggles, will also automatically apply to those of Member Functionality. This is because we are assuming that, in most cases, you will want to have the same settings for both clients and members. This ensures that you do not forget to change them for both.

Then, if you make any changes in Member Functionality directly, this will break the inheritance and cause an override, which will be further explained next.

Breaking Client to Member inheritance (override)

As mentioned above, whenever you change a toggle in the Member Functionality section, you will interrupt the sync with Client Functionality. This is because we are now assuming that you always want different settings for the two sets of users. If you go back to Client Functionality and change something, it will not reflect for members anymore.

This override does not work the same, however, for Functionality and Features toggles, here are the details:

• Functionality toggles - Changing a setting for members will break the sync only for that specific toggle. As an example, if I turn off Onboarding enabled for members, but I haven't touched the other two toggles, the sync with Client Functionality will only stop for Onboarding enabled.
• Enabled features toggles - Changing a setting for members will break the sync for all toggles. Enabled features act as a single block so, for example, if I turn off Video feedback for members, even if I haven't touched any of the other toggles, the sync with Client Functionality will stop for all of them regardless.

Allowing members mention

You will notice that both Client Functionality and Member Functionality have a dedicated section called Members that can be mentioned. This exclusively controls which members of your team can be mentioned in comments on feedback. Let's see how both can be set up:

1. Client Functionality - Members that can be mentioned (defaults to No members):

• No members: no one in your team can be mentioned by clients.
• All members: any of your team members who has access to the project will appear on the list to and can be selected to be mentioned by your clients.
• Selected members: only the selected members from this list can be mentioned by your clients.

2. Member Functionality - Members that can be mentioned (defaults to All members):

• No members: no one in your team can be mentioned by other team members.
• All members: any of your team members who has access to the project will appear on the list and can be selected to be mentioned by other team members.
• Selected members: only the selected members from this list can be mentioned by other team members.

There is no inheritance or override in place here; the settings must be configured manually on both sides.

Exporting a project

This feature allows you to export feedback and comments from specific projects into a CSV file. This is very useful if you want to have backups of your data (for example if you plan on archiving or deleting some projects), or to do custom reporting or analytics.

To access this option, simply open any active project, and then click the Export button on the right:

Once clicked, a box will open to ask you if you want to confirm the procedure.

A zip file will be downloaded, containing two different CSV files; one will contain information about feedback, and the other about threaded comments on the feedback. Let's now see in detail the information contained in these files.

1. project_{project.id}_feedback.csv - This is the file containing your feedback, and the columns are divided as such:

• id: identifier of the feedback that you can use to match with the comments of the other CSV file.
• type: whether this is a screenshot or recording feedback.
• resource: link to the actual screenshot or recording.
• title: the title of the submitted feedback.
• text: the description of the submitted feedback (can be blank).
• page: url of where the feedback was submitted.
• tags: tags added to the feedback (every tag will be within quotation marks, for example "Tag_1", "Tag_2").
• resolved: if the feedback was resolved, it shows the timestamp of when the action was done.
• reporter_name: first and last name of the person who submitted the feedback.
• reporter_email: the email address of the person who submitted the feedback.
• created_at: the timestamp of when the feedback was created.

2. project_{project.id}_feedback_comments.csv - This is the file containing the threaded comments for your feedback, and the columns are divided as such:

• feedback_id: you can use this to match the comments to your feedback in the id column of the other file.
• body: this is the actual text of the comment.
• reporter_name: first and last name of the person who submitted the comment.
• reporter_email: email address of the person who submitted the comment.
• created_at: the timestamp of when the comment was created.

Archiving a project

Archiving a project means that you will stop the feedback collection (so the Feedbucket widget will no longer be visible on websites where it's installed) and the project will be removed from the active project list inside Feedbucket Admin. This is a great way to clean up your Feedbucket admin without permanently deleting the project.

You can at any time restore the project from its archived state back to an active state, just like it was when you archived it.

To archive your project:

1. Go into your Project.
2. Click on Settings.
3. On the General tab, under Danger, you will see a button to Archive the project.
4. Click the Archive project button and confirm your action to archive the project. The pop-up will let you know that this action can be restored.

Permanently delete a project

If you do not want to archive the project but instead permanently delete it, you can do that too.

To delete the project:

1. Go into your Projects.
2. Click on Settings.
3. On the General tab, under Danger, you will see a button to Delete the project.
4. From here you can click the Delete project button and confirm. The pop-up will let you know that his action cannot be undone.

Frequently Asked Questions

• Can I have a project settings template so when I create a new project, those settings are automatically set?

This is possible, but not from your workspace directly at this time. You will need to contact our support, and we will be happy to create such a template for you. This feature will be coming in the future, so stay tuned! Also note that we will only be able to create one single template per account.

• Can I set default tags that will automatically be set when I create a new project?

Yes, this is something that can be done on our end as well, so please reach out to us if you need it. Please note that this will only work for native tags that have been created within Feedbucket, and not for tags synced from an integration (please check here for more details on this tag type).

• Can I set a default integration like the email integration when creating a project?

We do not support this for the time being, and this is valid for all integrations. Whenever you create a new project, you will also have to manually sync all of the integrations that you need.

Need Help?

If you have any questions, comments or feedback requests concerning projects, please do not hesitate to reach out to our support. You can easily contact us via the chat widget on the bottom right of this page.

Updated on: 23/06/2026