# Productlogz Demo ### ProductLogz Demo: Simplify Feedback and Feature Management πŸ‘©β€πŸ’» {% embed url="" %} With ProductLogz, you can effortlessly collect customer feedback, manage feature requests, and keep users updated on your future roadmap plans. I'll show you how to create feature requests, add them to your roadmap, and share your roadmap and feature request pages with your users. Additionally, I'll demonstrate how to create surveys, activate them, and analyze the feedback received. Join me to explore how Product Logs can transform your feedback and product development process. 00:00 Introduction 00:25 Signing up and Setup 01:00 Creating Feature Requests 01:24 Managing Roadmap 01:39 Sharing Roadmap and Feature Request Pages 01:56 Creating Surveys 02:25 Activating and Analyzing Surveys 02:42 Installation and Analytics 03:05 Rewarding Users # Collect feature requests/ ideas? ## Feature Request Board A feature Request board is where you can collect and see all your user’s requested features or ideas in one place as below.

Feature Request/ Idea board

Your users will be able to submit a new feature request by creating a post under create a post section and the same will be visible under **All feature requests Board**. **Public User:** A public user is one who has signed up on the platform to submit & interact with ideas board. In order for a user to create, submit, vote & comment on posts, he/she will have to sign up as Public User on the public feature requests board. Once a public user has signed up, his/ her user profile is created and he will be able to interact with admin & other user son the feature request board. **Private User**: A private user is one who has signed up to the platform to use the dashboard as an admin, moderator or team member. A private user will be able to interact with posts on the board, moderate comments & posts and add features to the product roadmap. **Vote & Comments**: All private & public users will be able to vote on existing feature requests and engage on others' posts with comments. When a feature request is created, 1 vote is automatically added for the first time. Top-voted features can then be picked for development. This will help you gauge which feature is most highly requested by your users and you will be able to prioritize your roadmap accordingly. **Categories**: You can add categories to your post to distinguish or categorize your posts under relevant topics like Integrations, Bugs, Improvements etc, Categories help you & your users to categorise, add & search relevant feedback under specific topics *** ## How to create a new feature request post? {% embed url="" %} * You can create a new feature request by submitting a new feature request post on your dashboard under Roadmaps- **Create Post**. * This will instantly reflect on your public feature request board. By default, the status is set to open. You can change the status to planned, in progress, or complete as and when your feature progresses in your roadmap. * To view what your Feature Request Board looks like, click on the Public Roadmap Link on your dashboard and Navigate to feature requests {% hint style="info" %} πŸ’‘ Tip: Publish your existing feature requests and ask your team members & users to upvote {% endhint %} *** ## How to collect feature requests from my users * You can collect feature requests from your users by sharing the Feature Request Link with your users. * When you log in to ProductLogz, your public feature request page will already be set up for you. * You can view all your feature requests by clicking on the Public Roadmap Link on your dashboard. Navigate to feature requests. This is a publicly shareable link. * Copy & paste the link on your website. Collect feature requests by sharing this link with your users in your email newsletter or share it in your socials {% hint style="info" %} πŸ’‘ Tip: Embed your Feature Request Link in your website & dashboard and ask your users at regular intervals to submit feature requests or vote on existing feature requests. {% endhint %} *** ## FAQs * **Are users required to be logged in to submit a feature request?** Yes, for now, if a user is not a logged-in/ existing customer, he/she will have to sign-up to submit a feature request. This is to ensure you know who has submitted the post and upvoted on feature requests. We will also allow guest posts at a later point in time. * **Do you allow guest submissions, voting & comments**?\ No we do not allow guest submission or interactions for now. Users have to sign-up or login to submit or interact with posts. We will be allowing guest submissions later. ## Related articles {% content-ref url="/pages/Jrp1yPFJg4PiZXCcfxD2" %} [Create your Roadmap](/create-your-roadmap) {% endcontent-ref %} {% content-ref url="/pages/KxzlsK9AKjbTjKVKrb7r" %} [Creating In App Surveys](/creating-in-app-surveys) {% endcontent-ref %} **Did we miss something?** Not to worry! Just email our support team at [contact@productlogz.com](mailto:team@getacme.co) ✌️ # Guest Posting Allow guests to submit & interact with posts! Guest Posting is a feature that allows non existing users to submit a post, upvote an existing feature request and engage on the post discussion. How to set-up Guest Post? By default, the ability of guest users to submit post or interact with existing posts is disabled. In order to enable or allow guests to submit & interact with posts, follow the following steps:
1. Step 1 : Go to settings 2. Step 2: Go to User Submissions 3. Step 3: Toggle the enable guest posting to enable guest submissions
Once guest posting is enabled your users/ visitors will be able to submit guest posts without having to register with ProductLogz or logging in. Your visitors/ users will have a choice to either register/ login or continue as guest to submit & interact with posts Once the user has continued as guest, an anonymous profile will be created and his/ her votes & submissions will be recorded.

Guest Posting Pop-Up

This feature is only available on PRO+ Plans. So if youο»Ώ are a PRO user, try it now or [*upgrade to the PRO plan* ](#user-content-fn-1)[^1] [^1]: # Create your Roadmap ## What is a Roadmap? Roadmap in Productlogz is a comprehensive view of the list of items or feature requests that you plan to build, are in development and have been completed. This helps your team to be aligned with your vision and be on-top of the build journey. ProductLogz allows you to publish Roadmaps for the visbility public users as well. This helps build trust & transparency between the company & it's users and also creates upsell opportunities on new & upcoming features. ## Setting up Roadmap Setting up Roadmap is very easy * When you log in to ProductLogz, your Public Roadmap Page will already be set up for you. If you have no feature requests, start by creating some from the section on the right under **Create Post.** Once you have populated features, the status is set to open by default. You can start adding items into you Roadmap by changing it's status to planned, in progress or complete. * Once you change the status on the feature requests, the items will be added to your Roadmap and you will be able to view the same under **Public Roadmap Link** * Feature requests items with status open mean that they are on hold or pending review before they can be added to the Roadmap. * Whenever you change the status of any feature request on the roadmap, your users will be able to see what features are planned/ in progress and are complete {% hint style="info" %} You can share your Roadmap with your users ( using the **Public Roadmap Link)** or embedding it into your dashboard. {% endhint %} ## Best Practices πŸ’‘ Filter by status to know which feature is at which stage πŸ’‘ Edit title & description to make your roadmaps more clear for your users πŸ’‘ Keep updating your roadmaps πŸ’‘ Share the Public Roadmap Link at regular intervals with your users over email/ social media πŸ’‘ Embed your Public Roadmap Link on your dashboard & website ## FAQs * **Can I delete any item under a Roadmap**? No. As of now, you do not have the option to delete any item under the Roadmap * **Are feature requests which are still in discussion displayed in the public Roadmap?** No. All feature requests/ posts which are pending review are by default set to OPEN status and are not displayed in the public roadmap. ## Related articles {% content-ref url="/pages/JeA9BwsbLpAIahxozSZK" %} [Collect feature requests/ ideas?](/collect-feature-requests-ideas) {% endcontent-ref %} {% content-ref url="/pages/KxzlsK9AKjbTjKVKrb7r" %} [Creating In App Surveys](/creating-in-app-surveys) {% endcontent-ref %} **Did we miss something?** Not to worry! Just email our support team at [contact@productlogz.com](mailto:team@getacme.co) ✌️ # Add thumbnails to your Roadmap items πŸš€ **Add Thumbnails to Your Roadmap Items!** πŸŽ‰
We’re excited to introduce a new way to make your roadmaps even more engaging and informative – **thumbnails**! Now, you can visually represent your planned features, helping users better understand what's coming up in a more engaging way. #### πŸ”Ž What Are Thumbnails? Thumbnails are small, image-based representations of your features. Instead of just text, you can now add images to roadmap items, making it easier for users to quickly grasp the essence of the feature. #### 🎯 What Purpose Do Thumbnails Serve? * **Pictorial representation**: Thumbnails add context by visually depicting what the feature is about. * **Engagement**: Visuals are more engaging than text alone, keeping your users more informed and excited about upcoming features. * **Clarity**: For complex features, thumbnails can serve as a quick, visual summary, helping users understand better. #### πŸ› οΈ How to Add Thumbnails: 1. Head over to your roadmap. 2. Select any roadmap item you want to add a thumbnail to. 3. Click the **'Add Thumbnail'** option. 4. Upload your image file, and you're good to go! #### ⚠️ Limitations to Keep in Mind: 1. **File size**: Make sure your image is under 1**MB**. 2. **Supported formats**: You can upload **JPEG, PNG, or JPG** files. 3. **Plan restrictions**: This feature is available only to users on our **PRO plan and above**. Get started today and make your roadmaps stand out with engaging thumbnails! πŸš€ # Creating In App Surveys ## In App Surveys In-app surveys are short questionnaires that are integrated into an app or a web-page. Using in app surveys you will be able collect feedback from users about their experience with a product or service. In-app surveys can help product teams identify ways to improve the user experience and customer satisfaction. ## How to Set Up an In-App Survey? * Create a survey by choosing one of the templates from under teh Survey module. * Give your survey a name and move on to the next step * Add your survey question. You can also preview how your survey will look on your website or app * Select the pages you want to show survey at. * Next, select the flow of your survey. You can show the survey to be shown immediately after the user lands on the page or after a delay of certain seconds * To install the survey, copy & paste the code provided under your Settings>> Survey **right before the \ tag of your website.** ## All Surveys You can see your list of created surveys and analytics for each survey with total views & clicks in your dashboard under All Surveys. ## Key Points to note: πŸ’‘ Only **1 survey** **will be active** in one account at a time. πŸ’‘ Survey will be shown to the user continuously unless it is closed or answered. πŸ’‘ Once users have **answered** the survey, another survey won't be shown for the next 30 days. πŸ’‘ If the user chooses to close the survey, it will not be shown for the next **1 hour.** ## Related articles {% content-ref url="/pages/dRmCzpPYF56x3fcotkrt" %} [Survey Analytics](/creating-in-app-surveys/survey-analytics) {% endcontent-ref %} {% content-ref url="/pages/fhLr1hmPzjXkTH4jPXbi" %} [Rewards](/rewards) {% endcontent-ref %} **Did we miss something?** Not to worry! Just email our support team at [contact@productlogz.com](mailto:team@getacme.co) ✌️ # Survey Analytics ### Survey Performance * **Last response:** Time when the user last answered the survey. * **Completion rate:** Percentage of users who have answered the survey. * **Views:** Once a user lands on the website, the survey will be shown to the user. ProductLogz starts the session for the user and it lasts for 1 day. The number of time the survey is shown to the user in this session is counted as a view. If the user closes the survey, it will not be shown for the next 1 hour. * **Unique views:** Total number of unique views on the survey in 1 session by 1 user. A session lasts for 1 day. If a user sees the survey 3 times in 1 session, it will be counted as 1 unique view. ## Related articles {% content-ref url="/pages/KxzlsK9AKjbTjKVKrb7r" %} [Creating In App Surveys](/creating-in-app-surveys) {% endcontent-ref %} {% content-ref url="/pages/fhLr1hmPzjXkTH4jPXbi" %} [Rewards](/rewards) {% endcontent-ref %} **Did we miss something?** Not to worry! Just email our support team at [contact@productlogz.com](mailto:team@getacme.co) ✌️ # Rewards ProductLogz offers a unique and powerful feature - ***Rewards for feedback participation*** By incentivizing users to provide feedback, you can get higher engagement, improved data quality, and faster feedback collection. ## **How do Rewards work?** * Start by creating a survey & select **rewards template** in step 2. * Once your survey is created, your users have the option to opt for rewards by entering their email while submitting the survey. * You will see all the users who have opted for rewards in the **Rewards section** of the dashboard ## Setting-up Rewards * Once you have activated surveys for your website/ app, your users will be eligible for rewards * You will be able to see the list of users who have opted in for rewards under your Rewards section * You can see the total feedback submitted by the user under the respective surveys and export the list as well. ## **How to reward your users?** Under the feedback rewards program, you can provide various incentives to users for their valuable feedback. Here are some ideas: * Discount Codes or Coupons: Offer exclusive discount codes or coupons that users can redeem on future purchases. * Gift Cards: Provide gift cards to popular retailers or online platforms as a token of appreciation for their feedback. * Early Access or Sneak Peeks: Give users early access to new features, products, or upcoming releases as a reward for their input. * Recognition or Badges: Acknowledge users publicly by highlighting their contributions, featuring their names, or awarding special badges. * **P.S: If you have any suggestions regarding the rewards program, kindly create a** [**Feature Request**](https://app.productlogz.com/company/productlogz/feature_requests) **& help us create a better rewards program.** ### **Related Articles** {% content-ref url="/pages/JeA9BwsbLpAIahxozSZK" %} [Collect feature requests/ ideas?](/collect-feature-requests-ideas) {% endcontent-ref %} {% content-ref url="/pages/KxzlsK9AKjbTjKVKrb7r" %} [Creating In App Surveys](/creating-in-app-surveys) {% endcontent-ref %} # Changelog A changelog is *a file that shares a chronologically ordered list of the changes you've made to your* product / project. Changelog helps your users know what the recent changes you have made to your product/ project ### How to Create a Changelog? You can create a Changelog by going into Changelog tab and clicking on the Create button Once you click on Create, a new tab will open up for you where you can insert a header Image, Title, Subtitle and content for your changelog Once you have created a changelog post, you can save it as a draft, preview it and publish it for your users to be able to see. If you are not prepared to publish your changelog post, you can save it as draft and return to the app later on to review and publish changes Once you hit publish, you will be able to see a log of your changelog post visible and accessible with all your users ### How to edit & format a Changelog Post You can edit your changelog post whenever you want to and publish changes to be reflected on the changelog page You can format your post with Bold/ Italic/ Underline and give headings as well If you wish to add author, subtitle and reactions to your post, you can enable these options on teh right side of your panel You can also assign tags such as New, Improvement & Fixes to your changelog post to categorize your post # Changelog Pop-Up Widget ## Changelog Pop-Up Widget What is a chaneglog Pop-Up widget? A changelog pop-up is a visually engaging notification or announcement that appears prominently on a website, or an app to inform users about recent changes, updates, or new features. It typically appears at the middle of the page or interface and provides a brief summary with a picture of what has been modified, added, or fixed in the latest version.
The purpose of integrating a changelog widget with visually engaging images is to provide users with a dynamic and captivating way to stay informed about the latest product updates. By combining text descriptions with images, this widget enhances user engagement and comprehension of the changes made to the software. ### How to enable Changelog Pop-Up Widget ? **Install Changelog pop-up** **Step 1**: Place this code right before the \ tag of your website. Replace company\_id with the code given under your dashboard settings>>widget. You will find your respective installation code under your `dashboard>>settings>>widget` ``` ``` **Step 2**: Enable changelog widget under Settings>>Widget>>**Enable Changelog Modal** **Step 3:** Add Rules to show the pop-up on specific pages.
### Rules 1. URL contains: By entering your specific URL, the widget will be shown only on the page which matches the URL entered 2. URL ends with: The widget will be shown only on pages where the URL ends with the specific keyword 3. Exact URL Match: The widget will be shown only on pages where the URL contains the specific keyword ### Conditions **Changelog Widget Conditions** 1. **The most recent published changelog will be shown in the pop-up/ banner** 2. **Once the user closes the widget, it won't be shown until next changelog is published** 3. **Banner & pop-up cannot be enabled at the same time** 4. **Once a user closes the widget in a given browser, it will not be shown till the next changelog is published** #### FAQ's
Can I change the text of the banners? No, by default the banner takes the text of the latest **active** changelog title that you have published. If you do not have any active changelog, the banner will be hidden.\ If you want to change the text or title, you can go to the Changelog tab and change it's header or text
Can i enable both banner & pop up No, only one can be enabled at a given point of time
How many times will the changelog pop-up be shown to the user The changelog widget will be shown only once, when a changelog is published. Once a user closes the widget in a given browser, it will not be shown till th enext changelog is published
# Changelog Banner ## Changelog Banner #### What are Changelog Banner ? A changelog banner is a notification or announcement that appears prominently on a website, or an app to inform users about recent changes, updates, or new features. It typically appears at the top of the page or interface and provides a brief summary of what has been modified, added, or fixed in the latest version.
Changelog banners are essential for keeping users informed about changes that may affect their experience or workflow. They help maintain transparency and trust between developers and users by keeping them updated on the latest developments and improvements. ### How to enable Changelog Banner ? **Install Changelog pop-up** **Step 1**: Place this code right before the \ tag of your website. Replace company\_id with the code given under your dashboard settings>>widget. You will find your respective installation code under your `dashboard>>settings>>widget` ``` ``` **Step 2**: Enable changelog widget under Settings>>Widget>>Enable Changelog Banner ### Conditions **Changelog Widget Conditions** 1. **The most recent published changelog will be shown in the pop-up/ banner** 2. **Once the user closes the widget, it won't be shown until next changelog is published** 3. **Banner & pop-up cannot be enabled at the same time** 4. **Once a user closes the widget in a given browser, it will not be shown till the next changelog is published** # Overview ProductLogz offers comprehensive team collaboration features, enabling you to invite team members, assign roles, and manage permissions across your workspaces. This guide provides comprehensive information on managing your team effectively. ### What You'll Learn In this documentation, you'll discover how to: * **Understand team roles** and their specific capabilities * **Add and manage team members** in your workspace * **Configure email notifications** for team activities * **Control access and permissions** for different team members ### Key Features Overview #### πŸ” Role-Based Access Control ProductLogz uses a role-based system where each team member is assigned specific permissions based on their role within your workspace. #### πŸ“§ Smart Notification System Team members receive email notifications based on their preferences and role, ensuring important updates reach the right people. #### πŸ‘₯ Workspace-Specific Permissions Team members can have different roles across multiple workspaces, providing flexible access control. #### πŸ’° Billing-Aware Team Limits Your subscription plan determines how many team members you can invite, with automatic enforcement during the invitation process. *** ### Quick Navigation | Section | Description | | ------------------------ | ------------------------------------------------------------- | | Team Roles & Permissions | Detailed breakdown of Admin, Manager, and Member capabilities | | Adding Team Members | Step-by-step guide to invite new team members | | Email Notifications | Configure notification preferences and understand delivery | | Team Settings | Manage existing team members and workspace settings | # Roles & Permissions ### Team Roles & Permissions ProductLogz supports three distinct team roles, each with specific capabilities designed to match your team's organizational structure. #### Administrator (`admin`) **Full access to all workspace features and settings** **Core Capabilities:** * βœ… **Team Management**: Add, edit, and remove team members * βœ… **Settings Access**: Full access to workspace and billing settings * βœ… **Content Management**: Create, edit, and delete all content * βœ… **Notification Control**: Configure notification preferences * βœ… **API Access**: Full access to all API endpoints **Key Responsibilities:** * Managing team member access and roles * Configuring workspace settings and integrations * Handling billing and subscription management * Overseeing content moderation and organization > **Important**: Administrators cannot edit or delete their own accounts. This prevents accidental lockouts from the workspace. #### Manager (`manager`) **Mid-level access with content management capabilities** **Core Capabilities:** * βœ… **Content Management**: Create and edit content * βœ… **Team Visibility**: View team member information * βœ… **Notification Control**: Configure personal notification preferences * ❌ **Team Management**: Cannot add or remove team members * ❌ **Settings Access**: Limited access to workspace settings **Key Responsibilities:** * Creating and managing roadmap content * Responding to user feedback and comments * Collaborating with team members on content #### Member (`member`) **Basic access with read permissions and limited content creation** **Core Capabilities:** * βœ… **Content Viewing**: Access to all published content * βœ… **Basic Interaction**: Comment and provide feedback * βœ… **Notification Control**: Configure personal notification preferences * ❌ **Content Management**: Cannot create or edit major content * ❌ **Team Visibility**: Limited access to team information * ❌ **Settings Access**: No access to workspace settings **Key Responsibilities:** * Providing feedback and comments * Collaborating on assigned tasks * Consuming and sharing content #### Permission Matrix | Feature | Admin | Manager | Member | | ---------------------------- | ----- | ------- | ------ | | **Team Management** | | | | | Add team members | βœ… | ❌ | ❌ | | Edit member roles | βœ… | ❌ | ❌ | | Remove team members | βœ… | ❌ | ❌ | | View team list | βœ… | βœ… | ❌ | | **Content Management** | | | | | Create roadmaps | βœ… | βœ… | ❌ | | Edit content | βœ… | βœ… | ❌ | | Delete content | βœ… | ❌ | ❌ | | Manage feedback | βœ… | βœ… | ❌ | | **Settings & Configuration** | | | | | Workspace settings | βœ… | ❌ | ❌ | | Billing management | βœ… | ❌ | ❌ | | Integration setup | βœ… | ❌ | ❌ | | **Notifications** | | | | | Receive admin notifications | βœ… | ❌ | ❌ | | Configure preferences | βœ… | βœ… | βœ… | | Test notifications | βœ… | ❌ | ❌ | # Adding Team Members ### Adding Team Members Only **administrators** can add new team members to your workspace. The invitation process is streamlined and includes automatic email notifications. #### Prerequisites > **Billing Check**: Before adding members, ensure your subscription plan allows additional team members. If you've reached your limit, you'll need to upgrade your plan first. #### Step-by-Step Process 1. **Navigate to Team Settings** * Go to Settings β†’ Teams * Click the "Add Member" button (visible only to admins) 2. **Enter Member Information** ``` Name: [Team member's full name] Email: [Valid email address] Role: [Select from Admin, Manager, or Member] ``` 3. **Role Assignment** * Choose the appropriate role based on the permission matrix above * Roles can be edited later if needed 4. **Automatic Invitation Process** * System generates a secure temporary password * Invitation email sent automatically * Member receives login credentials and workspace details #### Invitation Email Content New team members receive an email containing: * **Login URL**: Direct link to your workspace * **Temporary Password**: Auto-generated secure password * **Invited By**: Name of the administrator who sent the invitation * **Next Steps**: Instructions for first login and password change #### For Existing ProductLogz Users If the invited email address is already associated with a ProductLogz account: * User is automatically added to your workspace * No new password is generated * User receives a simplified invitation email * They can access your workspace immediately using existing credentials #### Team Size Limits by Plan | Plan | Maximum Team Members | | ---------- | ------------------------ | | Free | 1 (workspace owner only) | | Basic | 3 team members | | Pro | 10 team members | | Business | 25 team members | | Enterprise | Unlimited | > **Automatic Enforcement**: The system automatically prevents adding members beyond your plan's limit and will prompt you to upgrade if needed. # Email Notifications ProductLogz features a sophisticated notification system that keeps your team informed about important workspace activities. All notifications are delivered via email with customizable preferences. #### How Notifications Work **Default Behavior** * **All notifications are sent to administrators by default** * Individual team members can customize their notification preferences * Non-admin users receive notifications only for events they're specifically involved in **Notification Events** | Event Type | Description | Default Recipients | | ------------------ | ---------------------------------------- | ------------------------ | | **New Feedback** | User submits new feedback through widget | All admins | | **Status Changes** | Roadmap item status updated | All admins + subscribers | | **New Upvotes** | User upvotes a roadmap item | All admins | | **New Comments** | User adds comment to roadmap item | All admins + item author | #### Customizing Notification Preferences Every team member can configure their individual notification preferences: **Accessing Preferences** 1. Navigate to Settings β†’ Notifications 2. Toggle individual notification types on/off 3. Save preferences **Available Settings** ```markdown β˜‘οΈ New Feedback Notifications Notify when new feedback is submitted β˜‘οΈ Status Change Notifications Notify when roadmap statuses are updated β˜‘οΈ Upvote Notifications Notify when items receive new upvotes β˜‘οΈ Comment Notifications Notify when new comments are added ``` #### Notification Content Each notification email includes: * **Subject Line**: Clear description of the event * **Event Details**: Relevant information about what happened * **Direct Links**: Quick access to the specific item or feedback * **Context**: Author information and timestamps #### Admin-Only Features Administrators have additional notification capabilities: **Test Notifications (coming soon)** * Send test emails to verify notification setup * Available for all notification types * Accessible via Settings β†’ Notifications β†’ Test **Notification History (coming soon)** * View complete history of sent notifications * Track delivery status and failures * Monitor notification volume and patterns **Notification Statistics (coming soon)** * Count of notifications by type and status * Performance metrics for email delivery * Historical trends and patterns #### Email Delivery > **Reliable Delivery**: ProductLogz uses professional email services to ensure notifications reach your inbox. Check spam folders if notifications seem missing. **Email Configuration:** * **From Address**: `contact@alerts.productlogz.com` * **Delivery Method**: Immediate for most events * **Retry Logic**: Automatic retries for failed deliveries # Team Settings & Controls ### Team Settings & Controls The team management interface provides comprehensive controls for administrators to manage their workspace members effectively. #### Viewing Team Members **Team Overview** * **Location**: Settings β†’ Teams * **Information Displayed**: * Member name and email address * Current role in the workspace * Join date and status **Member Table** ``` | Name | Email | Role | Actions | |---------------|----------------------|---------|---------| | John Admin | john@company.com | Admin | [Edit] | | Jane Manager | jane@company.com | Manager | [Edit] [Delete] | | Bob Member | bob@company.com | Member | [Edit] [Delete] | ``` #### Editing Team Members Administrators can modify existing team member information: **Editable Fields** * βœ… **Name**: Update member's display name * ❌ **Email**: Cannot be changed after invitation * βœ… **Role**: Change between Admin, Manager, Member **Role Change Process** 1. Click the edit icon next to the member 2. Select new role from dropdown 3. Save changes 4. Member's permissions update immediately > **Email Restriction**: Email addresses cannot be modified after a member is added. To change an email, you must remove the member and re-invite them with the new address. # Language Support Productlogz allows you to offer a seamless experience to users across the globe by supporting multiple languages. With our Language Support feature, you can localize your public feedback boards. Productlogz enables you to cater to a global audience by offering multiple language options for your public feedback board and admin interface. This feature allows you to present key system-generated text in different languages, making it easier for non-English-speaking users to interact with your platform. {% hint style="info" %} **Available on all paid plans.** {% endhint %} #### What Is Translated: * **Public Feedback Board:** System-generated labels, buttons, and static interface text will be translated into the selected language. #### What Is Not Translated: * **User-Generated Content:** Any feedback, comments, or custom content submitted by users will remain in the language in which it was originally written. * **Admin Interface:** Productlogz’s admin dashboard will not support multiple languages yet. * **Dates and Numbers:** Regional formatting for dates, times, and numbers is **not supported yet**. These will continue to be displayed in the default format. *** #### How It Works: 1. Navigate to **Settings > Language**. 2. Select your preferred language for both the **Public Board**. 3. Productlogz will automatically translate all system-generated and static texts into the chosen language. 4. Users will experience the interface in their selected language, but content entered by other users will appear as-is. #### Supported Languages: We are continually expanding our language options. Visit the **Language Settings** page to see the latest list of supported languages. # Users The Users Module in ProductLogz allows you to manage and monitor user interactions with your roadmap and features. It provides detailed insights into user activities, helping you understand engagement #### 1. **View List of Users** * The module displays a list of all users who have interacted with your roadmap or contributed by adding features. * This list helps you identify active participants and track their contributions. #### 2. **User Details Overview** * Click on the **"view"** option next to any user to access their profile. * Inside the user detail page, you’ll find an **overview of all actions** performed by that user, including: * **Comments**: Feedback or discussions posted by the user. * **Posts**: Features or updates shared by the user. * **Upvotes**: Features or ideas the user has upvoted. * This detailed view helps you understand individual user engagement and contributions. #### 3. **Admin Identification** * Admins are marked with a **star icon (β˜…)** next to their name in the user list and detail view. * This makes it easy to identify users with administrative privileges at a glance. # Adding users to ProductLogz You can control how your users are authenticated before they start interacting ## Manual authentication Users can manually authenticate themselves by entering their email and password or signing in via Google. \ This process is simpleβ€”users just need to click the **Login/Signup** button. A popup will appear, allowing them to either login or create an account if they haven't already.
Clicking on the button will open a popup where your users can either create account if not created already.
With this method, user accounts are stored and authenticated by **Productlogz**. However, if you prefer to streamline this process, you can eliminate the manual authentication step for users. ## Automatically authenticating users You can use the below **Productlogz SDK Identify** method to remove the manual authentication step from the user's side. This way, they are automatically verified when they click the feedback link from your product. By integrating our JavaScript SDK, you can ensure that user feedback is linked to their accounts in your app. ### Step 1: Add the link to your product In your application, add the below link (replace `href` value) to your **Productlogz feedback portal**. Make sure it is prominently displayed so users can easily access it. 
```
<a data-pl-link href="https://company.productlogz.com" target="_blank">
   Give feedback
</a>
```
Make sure you replace `https://company.productlogz.com` with your public board link ( or your custom domain link). \ ⚠️ **Important:** The `data-pl-link` attribute must be included. If removed, authentication will not work. ### Step2: Add script tags Place the following code in your application codebase, primarily at the root or in index.html.
Modify the values to pass your application's user data. 
<script>
   window.ProductLogz('classify', {
      accountKey: <replace-with-your-account-id> // **required**,
      // NOTE: the 'user' is just used as a reference here, 
      // kindly replace it with your user's state.
      user: {
         alias: user.alias, // **optional**
         avatarURL: user.avatarURL, // **optional**
         createdAt: new Date(user.created).toISOString(), // **optional**
         email: user.email, // **required**
         id: user.id, // **required**
         name: user.name, // **optional**
         // **optional**
         companies: [
            {
               id: 'company-id',
               name: 'Company-Name',
               monthlyRevenue: some-number,
               createdAt: "2024-01-01",
            }
         ],
         // **optional**
         customFields: {
            title: 'Product Manager',
         }
      },
   });
</script>
#### **Required Configuration** **Account ID** * **`accountId`** `[string]` **(Required)** * Replace this value with your actual **account ID**, which can be found in the ProductLogz dashboard under **Settings > Workspace Details**. **User Fields** * **`id`** `[string]` **(Required)** * A unique identifier for each user in your system, ensuring their feedback is correctly linked to their account. * **`email`** `[string]` **(Required)** * The user’s email, making it easier to identify them and follow up on their feedback. * **`alias`** `[string]` **(Optional)** * A custom identifier for the user, useful if you want to reference them with something other than their email or user ID. * **`avatarURL`** `[string]` **(Optional)** * A URL for the user’s profile picture, helping personalize their feedback. * **`createdAt`** `[string]` **(Optional)** * The date and time the user was created in your system, useful for tracking feedback based on account age. * **`name`** `[string]` **(Optional)** * The user’s display name, making interactions more personal and recognizable. * **`companies`** `[array]` **(Optional)** * Associates a user with one or more companies, helping track feedback at an organizational level. * **`customFields`** `[object]` **(Optional)** * Attach additional metadata to a user, such as role, subscription plan, or other relevant attributes for better context. By implementing this setup, you can enhance the user experience while ensuring that their feedback is automatically linked to their account. πŸš€ *** ⚠️ Productlogz Identify doesn’t track admins, so if you’re testing, use a regular user account. [^1]: Replace this with your public page link here!! [^2]: Replace this string with your account ID. # Add Company Data to Productlogz Track feedback at the company level to gain deeper insights and prioritise the right features. Is your product built for businesses? If so, you likely have multiple user accounts tied to each company. To better organize and analyze feedback at the company level, you can send **company data** to **Productlogz** when identifying users. By doing this, Productlogz will not only track individual users but also associate their feedback with their respective companies. This allows you to: * **View company-level insights** – Understand how different organizations interact with your product and what features matter most to them. * **Prioritize feature requests more effectively** – See which requests have the biggest impact across multiple users within a company. * **Improve customer communication** – Get a clearer picture of which companies need attention based on their feedback trends. * **Identify high-value customers** – Use company-level data to track feedback from key accounts and prioritize their needs. #### **How to Send Company Data** When implementing the **Productlogz SDK Identify** method, simply include the `companies` field in the user object. This should contain relevant details about the company, such as: ```javascript ProductLogz('classify', { accountKey: // **required**, // NOTE: the 'viewer' is just used as a reference here, // kindly replace it with your user's state. user: { alias: user.alias, avatarURL: user.avatarURL, createdAt: new Date(user.created).toISOString(), email: user.email, id: user.id, name: user.name, companies: user.companies.map((company) => ( { id: company.id, name: company.name, monthlyRevenue: company.revenue, createdAt: new Date(company.created).toISOString(), } )) }, }); ``` * **name** – Helps you easily recognize which organization a user belongs to. * **id** – A unique identifier for tracking companies within your system. * **monthlyRevenue** – Useful for distinguishing feedback from different customer segments (e.g., free vs. enterprise). * **Signup Date** – Helps track feedback trends based on how long a company has been using your product. * **Custom Fields** – Attach any additional metadata relevant to your business needs. By leveraging company-level tracking in **Productlogz**, you gain deeper insights into your customers, helping you build a product that meets the needs of entire organizations, not just individual users. πŸš€ # ProductLogz and Notion Easily sync status updates between Notion and Productlogz to streamline feedback and feature request management. integration between Notion and Productlogz helps you manage feedback and feature requests more effectively by keeping your data in sync. This allows you to track status updates, streamline workflows, and avoid manual work. ### Benefits of This Integration #### 1. **Sync Status Automatically** With this integration, any status changes made in Notion will automatically update in Productlogz. Similarly, updates in Productlogz will reflect in Notion, ensuring both platforms stay aligned. #### 2. **Avoid Manual Updates** Instead of updating information separately in Notion and Productlogz, the integration syncs everything for you. This saves time and prevents errors caused by inconsistent data. #### 3. **Keep Teams Aligned** If your team uses Notion for documentation and Productlogz for managing feedback and feature requests, this integration ensures everyone stays informed without switching between tools. #### 4. **Improve Workflow Management** By linking Notion’s structured documentation with Productlogz’s feedback and roadmap features, you can track feature progress efficiently without missing important updates. #### 5. **Simple Setup** Connecting Notion with Productlogz takes only a few steps. Once linked, status updates and changes sync automatically, requiring no extra effort. ### How to Get Started 1. Go to the **Integrations** section in Productlogz. 2. Connect your Notion account and choose the relevant database. 3. Map the fields you want to sync, like **Status**. 4. Enable syncing and save your settings. Once set up, any changes in Notion or Productlogz will reflect in real time, making feedback and feature tracking more efficient. # Mapping status field Mapping Notion's Status Field to Productlogz Syncing your **Status** field between Notion and Productlogz allows for seamless tracking and management of your feature requests, feedback, and product updates. By mapping the **Status** field correctly, you ensure that changes in one platform are reflected in the other, keeping your team aligned and reducing manual updates. ### Why This is Useful * **Consistency Across Tools**: Keep your workflow synchronized without manually updating statuses in Notion and Productlogz. * **Real-time Updates**: Ensure that any status changes made in Notion are automatically reflected in Productlogz, and vice versa. * **Improved Workflow Management**: Helps product teams manage feedback and feature development efficiently. * **Automated Tracking**: Reduces errors and ensures stakeholders always have up-to-date information. ### How to Map the Status Field #### Step 1: Identify Status Fields in Notion and Productlogz * In Notion, locate the **Status** property in your database (e.g., "To Do," "In Progress," "Completed"). * In Productlogz, identify the corresponding status categories (e.g., "Planned," "In Development," "Shipped"). #### Step 2: Set Up Field Mapping 1. Go to **Integrations** in Productlogz. 2. Select **Notion Sync** and connect your Notion workspace. 3. Choose the Notion database where your feedback or tasks are stored. 4. Select the **Status** field from Notion and map it to the equivalent **Status** in Productlogz. 5. Save the mapping. # Slack Slack Integration Connect your Slack workspace to ProductLogz to receive instant notifications when customers submit feedback, and manage posts directly from Slack. *** ### Getting Started #### Connect Slack to ProductLogz 1. Go to **Settings > Integrations** in your ProductLogz dashboard 2. Find the **Slack** card and toggle it **on** 3. A Slack authorization window will open β€” select the workspace you want to connect 4. Click **Allow** to grant ProductLogz the required permissions 5. You'll be redirected back to your dashboard with a success confirmation After connecting, you'll see a prompt to configure your notification channel. Notifications won't be sent until you complete this step. #### Configure Notifications 1. On the Slack integration card, click the **Settings** (gear) icon 2. Select a **Notification Channel** from the dropdown β€” this is where ProductLogz will post alerts * Both public and private channels are supported * Private channels are marked with a lock icon 3. Check **Enable Slack Notifications** to turn on alerts 4. Click **Save Settings** > **Note:** The ProductLogz bot must be a member of the selected channel. It will automatically join public channels when the first notification is sent. For private channels, you'll need to manually invite the bot by typing `/invite @ProductLogz` in the channel. *** ### Features #### 1. New Feedback Notifications When a customer submits feedback on your public board, ProductLogz sends a notification to your configured Slack channel. **The notification includes:** * Feedback title and description (first 200 characters) * Category * Status **What you see depends on your Post Moderation setting:** **If Post Moderation is ON** β€” the notification includes **Approve** and **Trash** action buttons so you can review feedback without leaving Slack. ``` ----------------------------------------- New Customer Feedback *Allow dark mode in the app* It would be great to have a dark mode option for the dashboard... Category: Feature Status: Pending [Approve] [Trash] ----------------------------------------- ``` **If Post Moderation is OFF** β€” the notification includes a **View Feedback** link to open the post in your ProductLogz dashboard. ``` ----------------------------------------- New Customer Feedback *Allow dark mode in the app* It would be great to have a dark mode option for the dashboard... Category: uncategorized Status: open View Feedback in ProductLogz ----------------------------------------- ``` *** #### 2. Approve or Trash Feedback from Slack When Post Moderation is enabled, you can approve or trash feedback posts directly from the Slack notification β€” no need to open your dashboard. * Click **Approve** to set the post status to "open" and make it visible on your public board * Click **Trash** to reject the post After clicking a button, the notification updates to show the action taken and who performed it: ``` ----------------------------------------- New Customer Feedback *Allow dark mode in the app* ... Category: Feature Status: Approved Approved by @yourname | View in ProductLogz ----------------------------------------- ``` *** #### 3. Send Slack Messages to ProductLogz You can turn any Slack message into a ProductLogz feedback post β€” useful for capturing feature requests or bug reports that come up in team conversations. **How to use:** 1. Hover over a message in Slack 2. Click the **three-dot menu** (More actions) 3. Select **Send to ProductLogz** 4. A form will open pre-filled with the message content: * **Title** β€” auto-generated from the message text (editable) * **Description** β€” full message content * **Category** β€” choose from Feature, Bug, Improvement, or Other * **Customer Email** β€” optionally add the customer's email for tracking 5. Click **Submit** The feedback post is created in ProductLogz. If Post Moderation is enabled, it will be set to "pending" for admin review. Otherwise, it goes live immediately. A confirmation message will appear in Slack with a link to view the feedback in your dashboard. *** #### 4. Disconnect Slack You can disconnect the integration at any time: 1. Go to **Settings > Integrations** 2. Toggle the Slack integration **off** 3. Confirm the disconnection This removes the connection between your ProductLogz workspace and Slack. All Slack-related metadata stored on feedback posts will also be cleared. > **Note:** If someone uninstalls the ProductLogz app directly from your Slack workspace (via Slack's App Management), the integration will be automatically disconnected on the ProductLogz side as well. *** ### FAQ **Q: Which events trigger a Slack notification?** Currently, Slack notifications are sent when new feedback is submitted on your public board. Email notifications cover additional events like status changes, upvotes, and comments β€” these can be configured in your notification preferences. **Q: Why am I not receiving Slack notifications?** Check the following: 1. The Slack integration is connected (toggle is on) 2. A notification channel is selected in settings 3. Notifications are enabled (checkbox is checked) 4. The ProductLogz bot has access to the channel β€” for private channels, invite the bot with `/invite @ProductLogz` **Q: Can I change the notification channel later?** Yes. Click the Settings icon on the Slack card, select a different channel from the dropdown, and save. **Q: What happens if I reinstall the Slack app?** Your notification channel and settings are preserved when you reinstall. You don't need to reconfigure anything. **Q: Do Slack notifications work with private channels?** Yes. Select a private channel from the dropdown in settings. Make sure the ProductLogz bot is invited to the channel.