Skip to main content
Version: 1.40

Account preferences notifications and keys

The account section provides users with a centralized interface to manage their account settings. Users can customize their experience by configuring default workspace preferences, language settings, and notification preferences. Additionally, users can generate and manage personal key pairs for secure API and Python client interactions.

Account preferences​

Accessing the account section​

To access the Account section, log in to your account and navigate to the user avatar located in the top-right corner of the application. Click on your username and select "Account" from the dropdown menu.

Default workspace​

The Default Workspace setting allows users to set a preferred workspace that will be automatically selected upon logging in. This streamlines the user experience by directing them to their preferred environment without manual selection.

Instructions​

  1. In the Account section, locate the "Default Workspace" dropdown.
  2. Choose the desired workspace from the available options.
  3. Click the "Save" button to apply the changes.

Language​

Language settings enable users to customize the application's interface language to suit their preferences.

Instructions​

  1. Find the "Language" dropdown in the Account menu.
  2. Select the preferred language from the dropdown menu.
  3. Click "Save" to update the language settings.

Notifications​

Notification preferences empower users to manage how they receive notifications from the application. Users can opt to receive notifications via email, in-app messages, or both.

Instructions​

  1. Navigate to the "Notifications" section.
  2. Choose notification preferences based on your desired communication channels.The upper checkbox allows you to deselect all checkboxes
  3. Save the changes to update your notification settings.

Notifications​

The notification center serves as a centralized hub where users can conveniently view all notifications received on their account. This feature provides users with the ability to filter notifications based on event type and read status.

Filtering notifications​

  1. Event Type: Filter notifications by selecting a specific event type from the available options. This helps users focus on notifications related to particular activities.
  2. Read Status: Filter notifications based on whether they have been read or are still unread. This feature aids in organizing and managing notifications efficiently.

Interacting with notifications​

  • Click a notification: this will route a user to the section in the product where the notification originated from (e.g., monitoring alert). After clicking a notification it will be marked with the read status.
  • Mark a notification as read: next to clicking the notification a notification can also be marked as read by clicking the three dots at the right side of the notification that appear when hovering over it. Locate and click the Mark as read option. As an alternative all current unread notifications can be marked as read by clicking the Mark all as read button at the upper right corner of the notification center.
  • Delete a notification: by clicking the three dots at the right side of the notification that appear when hovering over it a notification can be deleted. Locate and click the *Delete option.

Event types​

The Notification Center supports various event types, each associated with a specific activity or update within the system. Common event types include:

  • Configured alters: Notifications about alerts that have been triggered in your workspace
  • Deployment change: Notifications about changes or updates to the user's deployments.
  • Workspace changes: Notifications about changes or updates to the user's workspace.
  • Repository changes: Notifications about changes or updates to the repositories in a user's workspace.

Understanding the event types helps users quickly identify the nature of each notification and prioritize their response accordingly.

Personal keys​

Personal keys facilitate secure interactions with the Deeploy API and Python client. Users can generate, manage, and revoke key pairs as needed. Personal key is linked to your user authorisations on an account level.

Generating a new key pair​

  1. Access the Create personal key section.
  2. Add a key name and optional valid until date
  3. Click + Add to generate a key pair
  4. Store the generated key pair (especially the secret key) securely. The key pair can be used for API and Python client authentication.
info

Be sure to save the secret key carefully as it will only be shown once

Delete a key pair​

  1. In the Keys section, view the list of generated key pairs.
  2. Locate the key pair to be deleted.
  3. Click the red bin to delete an existing key pair.

Using Key Pairs with the API and Python Client​

Provide the public key when making API requests for authentication. For Python client interactions, use the private key for secure communication. Keep key pairs confidential and never share the private key.

Beware

Deleting personal keys cannot be undone