# Profile Tab

## Profile Tab

The Profile tab is the administrative settings area of your organization.It controls:

* Organization identity
* Structural management
* Subscription lifecycle

Access to this tab depends on role:

* **Owner** → Full access
* **Admin** → Can edit most settings
* **Member** → No access

***

## 1. Organization Information

The Organization Information section defines the identity of your organization within Qolaba.It includes:

* Organization logo
* Organization name

This section allows Owners and Admins to customize and maintain the organization’s profile.

***

### Upload Organization Logo

You can upload a logo to visually represent your organization.

#### Purpose of Organization Logo

* Displays branding across the organization dashboard
* Improves team identification
* Helps members distinguish between multiple organizations
* Strengthens professional presentation

For agencies managing multiple organizations or consultants working with multiple clients, this helps avoid confusion when switching between accounts.The logo is purely organizational branding — it does not affect credit usage or functionality.

***

### Edit Organization Name (Owner & Admin Only)

Owners and Admins can modify the organization name at any time.

#### Why Editing May Be Needed

* Rebranding
* Company name change
* Department restructuring
* Project-to-company transition

The organization name:

* Appears in member invitations
* Appears in profile dropdown
* Appears in dashboard headers

#### Role Restriction

Members cannot edit the organization name.This ensures identity consistency and prevents accidental renaming.

***

## 2. Organization Management

This section controls the structural existence of the organization.It includes one critical action:Delete Organization

***

### Delete Organization

This action permanently removes the organization from Qolaba.

#### Access Restriction

Only the **Owner** can delete an organization.Admins cannot delete the organization.This ensures:

* Maximum structural security
* Protection from accidental deletion
* Clear authority boundary

***

#### What Happens When an Organization Is Deleted

Deleting an organization will:

* Remove all workspaces
* Remove all members
* Remove usage history
* Remove billing association
* Permanently erase associated data

This action **cannot be undone**.Once deleted:

* Credits are lost
* Workspace history is removed
* Member access is revoked
* Data cannot be recovered

***

#### When Should You Delete an Organization?

* Company closure
* Project termination
* Migration to a new organization
* Complete discontinuation of service

For temporary discontinuation, canceling subscription is safer than deleting.

***

## 3. Subscription Management

This section controls the lifecycle of your paid plan.It allows Owners and Admins to cancel active subscriptions.

***

### Cancel Subscription

Owners and Admins can cancel the organization’s subscription.Canceling subscription:

* Stops automatic renewal
* Does not immediately disable access

***

#### What Happens After Cancellation

If you cancel:

* Your subscription remains active until the end of the current billing cycle
* Credits remain usable during that period
* After expiration, premium access is discontinued

This ensures:

* No sudden workflow interruption
* Predictable offboarding
* Smooth transition planning

***

#### Important Distinction

Cancel Subscription ≠ Delete OrganizationCanceling:

* Stops future billing
* Keeps organization structure intact
* Ends premium features after billing period

Deleting:

* Permanently removes organization and all data

###


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.qolaba.ai/organization-and-workspaces/organizations/organization-dashboard/profile-tab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.