Visibility Settings

Three Visibility Options:

Choosing the Right Level:

PUBLIC:

• Default choice for most products
• Any logged-in user can view and participate
• Ideal for customer-facing products
• Maximizes feedback collection

RESTRICTED:

• Selective access via grants
• Good for beta programs
• Partner-only features
• Segment-specific products

INTERNAL:

• Employee-only feedback
• Internal tool improvements
• Confidential product development
• Team-specific ideas

Setting Visibility on a Product:

During Creation:

1. Go to Admin → Products → Create Product
2. Find the Visibility section
3. Select your desired level
4. Complete product creation

Editing Existing Product:

1. Go to Admin → Products
2. Click on the product to edit
3. Navigate to Settings tab
4. Change the visibility level
5. Save changes

Important Considerations:

• Changing visibility takes effect immediately
• Users may lose access if you restrict
• Existing votes remain intact
• Notify users before major changes

Public Visibility Deep Dive:

Who Can Access:

• Any authenticated (logged-in) user
• Anonymous users cannot access

What They Can Do:

• View all ideas in the product
• Submit new ideas
• Vote on ideas
• Comment on ideas
• Follow the product

Settings for Public Products:

• Enable/disable submissions
• Enable/disable anonymous voting (if supported)
• Set submission guidelines
• Configure required fields

Use Cases:

✓ Main product feedback

✓ Feature requests

✓ Community ideas

✓ Open roadmap input

Restricted Visibility Deep Dive:

Access Requirements:

• User must be authenticated
• User must have explicit access grant
• Access can be individual or group-based

Managing Access Grants:

See Access Control for details

Grant Types:

Best Practices:

• Document access criteria
• Review grants periodically
• Communicate with affected users
• Provide access request process

Internal Visibility Deep Dive:

Who Can Access:

• Users with Employee role or higher
• Tenant Admins
• Super Admins

Automatic Access:

No grants needed - role determines access

Use Cases:

• Internal tool feedback
• Employee idea programs
• Pre-launch product development
• Confidential improvements

Security Considerations:

• Ideas may contain sensitive info
• Ensure proper role assignments
• Audit access regularly
• Consider separate instances for highly sensitive data

Reviewing Visibility Settings:

Product Visibility Report:

1. Go to Admin → Products
2. View visibility status for each product
3. Filter by visibility level

Access Audit:

For restricted products:

1. Click on the product
2. Go to Access tab
3. Review all users with access
4. Identify unnecessary grants

Recommended Review Schedule:

Audit Checklist:

☐ Is visibility level still appropriate?

☐ Are access grants current?

☐ Any departed employees with access?

☐ Customer segments correct?

Scenario 1: Beta Launch

1. Create product with RESTRICTED visibility
2. Grant access to beta participants
3. Collect focused feedback
4. Change to PUBLIC at general launch

Scenario 2: Partner Program

1. Create RESTRICTED product
2. Create customer groups for partners
3. Grant access to partner groups
4. Partners can submit and vote

Scenario 3: Internal → Public

1. Start with INTERNAL visibility
2. Employees develop initial ideas
3. Team refines and prioritizes
4. Change to PUBLIC to include customers

Scenario 4: Segment Testing

1. RESTRICTED product
2. Grant to specific customer segment
3. Test feature interest
4. Use data for roadmap decisions