# Profile

Your **Profile** is where you manage your organisation details, members, permissions, alerts, API keys, and profile settings. It also provides visibility into data access logs for compliance and auditing.


---

## Organisation Details

Update your organisation’s basic information:

* **Organisation name**
* **Physical address**
* **Billing address**

This ensures accurate records and billing information across your account.


---

## Members

View and manage all members in your organisation:

* Invite new members.
* See pending invites.
* Assign or update role permissions via **Profile > Members > Actions > Modify Permissions**.


---

### User Permissions

Each member of your organisation can have one of the following roles:

* **Owner** – The original creator of the organisation. Full access, including deleting the organisation. Only one owner can exist at a time.
* **Admin** – Full management of the organisation, including members, campaigns, and billing.
* **Member** – Can view and edit contacts and campaigns.
* **Viewer** – Read-only access to basic information. Cannot view personal contact details, update, or delete.
* **Custom** – Fully customisable permissions. Toggle specific capabilities on/off for fine-grained access control.

> **Best Practice:** Assign the minimum level of access required for each member’s responsibilities.


---

## Alerts

Configure **event-driven notifications** so you’re always aware of key account activities.

Alerts can be sent to:

* **Email** (multiple addresses allowed, separated by commas).
* **Slack** (via integration).

**Available Alerts:**

* **Failed Send Alert** – Triggered if an SMS send fails.
* **Low Credits Alert** – Notifies you when credits fall below a threshold.
* **Low New Contacts Alert** – Triggers if fewer than a set number of new contacts are added within the last 24 hours.
* **Failed Hook Alert** – Notifies you if a campaign hook fails.


---

## API Keys

Generate API keys to integrate with the **Dripcel API**.

* Each key has **roles/permissions**, just like organisation members.
* Permissions can be defined at creation or later modified under the API Keys page.


:::warning
⚠️ **Important:**  
By default, API keys inherit the permissions of the user who created them — which may be more than necessary. Always apply the principle of least privilege when generating keys.

:::


---

## Settings

Manage your account preferences:

* **Change password**
* **Delete account** (irreversible)


---

## Data Access Logs

Track **who accessed your data** and when, for compliance and security auditing.

Available filters:

* **User** – Organisation member who accessed data.
* **IP Addresses** – Comma-separated IPs.
* **Action Path** – API path of the accessed data.
* **Date Range** – Filter by timeframe.

You can also **download logs** for external auditing or record-keeping.