Project overview

This page is the central hub for managing your project. It shows key sections, settings, and team members, allowing you to configure API access, display presets, and control project access.

Quick actions

• Click API Keys or Display Presets to expand sections and manage them.
• Use the Edit icon to modify project details like name, description, and color.
• Click the Doorbell icon to view notifications for this project.
• Access Analytics via the graph icon for performance insights.

Page layout

The project page contains these main areas:

1. Project header with name, description, and action icons.
2. API Keys section for managing API access.
3. Display Presets section for notification styling options.
4. Members section for team management.

Project header

Project identification

The header shows your project's name, description, and a colored dot for quick visual identification. The color dot appears in project lists throughout the interface and helps you spot the right project at a glance. You can customize the color when creating or editing the project.

Action icons (from left to right):

• Doorbell – Opens the notifications page for this project
• Graph – Opens analytics and performance metrics
• Edit – Opens project settings to modify name, description, URL, or color
• Close – Returns to the projects list

API Keys

Manage API keys for integrating your application with Korrero. By default, this section is collapsed.

API key purpose

API keys authenticate your application and control access to notifications and analytics for this specific project.

Viewing API keys

1. Click the API Keys header to expand the section.
2. View existing keys in the list format.
3. Each key shows:
   • The key value (partially masked for security).
   • Creation date.
   • Settings and Delete action buttons.

API key security

• Keys are public and safe to include in client applications.
• Each project can have multiple keys for different environments or integrations.

Creating API keys

1. Click + Add API Key in the API Keys section.
2. (Optional) Configure advanced settings in the dialog (see API Key Configuration).
3. Click Create to generate the key.
4. Copy and store the key securely – it won't be shown again.

Advanced configuration

For detailed API key settings and developer options, see the API Keys Configuration section.

Display Presets

Configure how notifications appear across your application. This section is collapsed by default.

Preset types

• System presets are built-in and cannot be disabled or deleted.
• Custom presets are user-created and can be modified or removed.

Viewing presets

1. Click Display Presets to expand the section.
2. Browse available presets with their names, descriptions, and types.

Creating custom presets

1. Click + Add Preset in the Display Presets section.
2. Fill in the required fields:
   • Name (required): 3-50 characters, letters, numbers, and hyphens only.
   • Description (optional): Brief explanation of the preset's purpose.
3. Configure display settings (colors, sizing, positioning, etc.).
4. Click Create to save.

Preset requirements

• Names must be 3-50 characters and contain only letters, numbers, and hyphens.
• System presets (built-in options) cannot be edited or removed.
• Custom presets only affect this project – they won't appear in other projects.
• Custom presets act as identifiers in the API and won't show up in automatic rendering mode.

Disabling custom presets

You can disable custom presets you no longer need. Once disabled, they won't appear in the preset dropdown when creating or editing notifications.

Existing notifications

Disabling a custom preset won't affect notifications that are already using it – they'll continue to work exactly the same way.

Members section

Manage team access and permissions for the project.

Team management

Control who can view, edit, or administer the project through role-based permissions.

Viewing members

1. Click on the Members icons.
2. See all current team members with their roles and email addresses.

Adding members

1. Use the search field to find users by email address.
2. Select users from the dropdown results.
3. Click + Add member
4. Assign appropriate roles (see Role comparison).

Managing roles

Click the role dropdown next to any member to change their permissions. Changes take effect immediately.

Role comparison

Role behaviors

• Owner: Has complete control but cannot leave (would delete the project). Can transfer ownership to another member.
• Administrator: Can manage all aspects except project deletion and ownership transfer.
• Viewer: Read-only access; cannot modify anything.

Role	View Notifications	Create/Edit/Delete Notifications	Manage API Keys	Manage Display Presets	Manage Members	Delete Project	Notes
Owner	✅	✅	✅	✅	✅	✅	Full control. Cannot leave project (would delete it). Transferring ownership demotes current owner to Admin.
Administrator	✅	✅	✅	✅	✅	❌	Can manage all aspects except project deletion and ownership transfer.
Viewer	✅	❌	❌	❌	❌	❌	Read-only access to notifications and settings.

Admin demotion

Only Owners can demote Administrators to Viewers. Administrators cannot demote other Administrators or change ownership.

API Key Configuration

When creating or editing API keys, you can configure these settings:

Setting	What it does	Default value	Why it matters
API Key	The actual key used to authenticate with the API	Auto-generated (e.g., "proj_xxx...xxx")	This is your API key - copy and use it in your application code to authenticate API requests.
Time Scope	Which notifications the key can access	Current and Future	Controls whether your app sees past notifications or only upcoming/active ones.
Sort Order	How notifications are ordered in responses	Newest first	Useful if your app needs notifications in a specific order (oldest first for chronological feeds).

Developer resources

For complete API key management and integration details, see the API Reference page.

Tips for project management

Best practices

• Use descriptive names for API keys and presets to avoid confusion.
• Regularly review members and remove inactive users.
• Customize the project color dot to match your branding or make it easily identifiable.
• Keep preset descriptions clear so team members understand their purpose.

Project organization

• Each project is independent with its own notifications, members, and settings.
• API keys and presets are project-specific and don't affect other projects.
• Consider creating separate projects for different applications or environments (dev/staging/production).

Troubleshooting

Common issues

• Can't see notifications? Check if you're in the right project and have appropriate permissions.
• API key not working? Verify the key value and ensure it hasn't expired.
• Preset not appearing? Confirm it's enabled and supported by your client application.
• Member not receiving invites? Check if their email is correct and they're not already a member.

For project-specific issues, contact support.