> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apinizer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Developer Multi Portal Usage

> Steps for creating and managing new API Developer Portal on Apinizer. Each portal works completely isolated with independent configuration, theme, and access control.

## What is Multi Portal?

**API Developer Multi Portal** feature allows you to create and manage multiple independent API Developer Portals on the Apinizer platform. Each portal works as a completely independent environment with its own users, APIs, settings, and appearance.

### Simple Explanation with Examples

Imagine you are a company serving different groups:

**Scenario 1: Different Departments**

* **Sales Team Portal:** Special APIs and documentation for your sales team
* **Customer Service Portal:** Different APIs for your customer service team
* **IT Department Portal:** Advanced APIs for technical team

**Scenario 2: Different Customer Groups**

* **Partner Companies Portal:** Special APIs for your business partners
* **General User Portal:** Public APIs
* **Premium Customer Portal:** Premium APIs for your special customers

**Scenario 3: Different Environments**

* **Test Portal:** For development and testing
* **Production Portal:** For live system
* **Demo Portal:** For demonstrations and demos

Each portal is like a separate website working on its own. Changes you make in one do not affect others.

### Multi Portal Advantages

<CardGroup cols={2}>
  <Card title="Independence" icon="building">
    Each portal has its own settings, users, and APIs. Changes made in one portal do not affect others.
  </Card>

  <Card title="Customization" icon="paintbrush">
    You can use different logo, color scheme, theme, and content for each portal. Each portal can have its own brand.
  </Card>

  <Card title="Security and Isolation" icon="shield-halved">
    Each portal has its own security settings. Users can only access portals they are authorized for.
  </Card>

  <Card title="Flexibility" icon="sliders">
    You can activate different features for different portals. For example, Analytics can be open in one and closed in another.
  </Card>

  <Card title="Management Ease" icon="users-gear">
    You can assign different administrators for each portal. Departments can independently manage their own portals.
  </Card>

  <Card title="Scalability" icon="chart-line">
    You can create as many portals as you need. Each portal can be scaled separately.
  </Card>
</CardGroup>

### How Does Multi Portal Work?

**Single Platform, Multiple Portals**

On the Apinizer platform, you can manage all your portals from a single management panel:

1. **Portal Creation:** When you create a new portal, the system automatically:
   * Creates a unique URL for the portal
   * Allocates a separate database area
   * Prepares an independent working environment

2. **Portal Management:** For each portal:
   * You can configure its own settings
   * You can add its own users
   * You can publish its own APIs
   * You can customize its own appearance

3. **Portal Access:** Each portal:
   * Has its own URL (e.g., `https://api.company.com/portal/partner-portal`)
   * Has its own login page
   * Has its own user accounts

### Portal Isolation

Each portal works in a completely isolated structure technically:

| Component     | Description                                                         |
| ------------- | ------------------------------------------------------------------- |
| **Namespace** | Each portal works in its own namespace, separate from other portals |
| **Pod**       | Each portal works in its own working unit (pod)                     |
| **Secret**    | Each portal has its own security keys and passwords                 |
| **Service**   | Each portal has its own service configuration                       |

Thanks to this isolation:

* A problem occurring in one portal does not affect others
* Security vulnerabilities do not spread from one portal to another
* Performance issues remain isolated

### Independent Configuration

All settings and configurations of each portal are independent from each other:

<AccordionGroup>
  <Accordion title="Appearance and Theme Settings" icon="palette">
    Different for each portal:

    * Logo and brand image
    * Color scheme (primary color, secondary color, background)
    * Font settings
    * Home page content
    * Footer content

    **Example:** You can use your company logo in partner portal, and a different logo in general portal.
  </Accordion>

  <Accordion title="Security and Access Control" icon="shield-halved">
    Different for each portal:

    * User registration permissions (open/closed)
    * Auto approval settings
    * API subscription approval processes
    * Credential management permissions
    * IP restrictions

    **Example:** Auto approval can be open in partner portal, manual approval may be required in general portal.
  </Accordion>

  <Accordion title="User and Role Management" icon="users">
    Different for each portal:

    * User accounts (a user can register to multiple portals)
    * User roles and permissions
    * Portal administrators
    * Organization structures

    **Example:** The same person can be in both partner portal and general portal with different roles.
  </Accordion>

  <Accordion title="API and Content Management" icon="code">
    Different for each portal:

    * Published API products
    * API documentation
    * Pricing plans
    * Content pages
    * Files and resources

    **Example:** Premium APIs can be published in partner portal, basic APIs in general portal.
  </Accordion>

  <Accordion title="Feature Settings" icon="puzzle-piece">
    Different for each portal:

    * Try It Out (test console) active/passive
    * Analytics feature active/passive
    * Jira integration active/passive
    * How to Use menu active/passive

    **Example:** All features can be open in premium portal, only basic features can be open in basic portal.
  </Accordion>

  <Accordion title="Language and Localization" icon="globe">
    Different for each portal:

    * Default language (Turkish/English)
    * Multi-language support (open/closed)
    * Language content

    **Example:** Turkey portal can be Turkish, global portal can be English.
  </Accordion>
</AccordionGroup>

### When Should You Use Multi Portal?

It is recommended to use Multi Portal feature in the following situations:

<Tabs>
  <Tab title="Different Customer Segments">
    **Usage Scenario:**

    * You offer different APIs to different customer groups
    * You want a special portal for partner companies
    * You want to offer a separate experience for premium customers

    **Advantage:** Each customer group experiences a portal experience customized according to their needs.
  </Tab>

  <Tab title="Different Departments/Units">
    **Usage Scenario:**

    * Different departments within the company want to manage their own APIs
    * Each department wants to independently manage their own portals
    * You want to control data sharing between departments

    **Advantage:** Each department independently manages their own portals, central control is provided.
  </Tab>

  <Tab title="Different Environments">
    **Usage Scenario:**

    * You want separate portals for test and production environments
    * You want a separate portal for demo and presentations
    * You want to keep development processes isolated

    **Advantage:** Changes in test environment do not affect production, safe development is done.
  </Tab>

  <Tab title="Different Regions/Languages">
    **Usage Scenario:**

    * You want localized portals for different countries/regions
    * You want different language and content for each region
    * You want to comply with local regulations

    **Advantage:** Each region experiences a portal experience in their own language and culture.
  </Tab>
</Tabs>

### Multi Portal vs Single Portal

| Feature             | Single Portal                    | Multi Portal                              |
| ------------------- | -------------------------------- | ----------------------------------------- |
| **User Management** | All users access the same portal | Each portal has its own users             |
| **API Management**  | All APIs in one place            | Each portal publishes its own APIs        |
| **Customization**   | Single appearance                | Each portal can have different appearance |
| **Security**        | Single security policy           | Each portal has its own security settings |
| **Management**      | Central management               | Each portal can be managed independently  |
| **Flexibility**     | Limited                          | High flexibility                          |
| **Complexity**      | Simple                           | More complex (but more powerful)          |

### Summary

**Multi Portal** allows you to create and manage multiple independent API Developer Portals on the Apinizer platform. Each portal:

✅ Has its own users\
✅ Publishes its own APIs\
✅ Has its own appearance\
✅ Has its own settings\
✅ Works completely independently

This way, you can offer customized portal experiences for different customer groups, departments, or environments, and manage each one independently.

<Tip>
  Multi Portal feature is ideal for large organizations and companies serving different customer segments. A single portal may be sufficient for small-scale projects.
</Tip>

## Prerequisites

<Warning>
  **API Developer Multi Portal Installation** must be completed to add a new API Developer Portal.
</Warning>

Please review the [API Developer Multi Portal Installation](/en/setup/apinizer/api-multi-portal) documentation for installation.

## Portal Listing and Viewing

### Accessing Portal List

<Steps>
  <Step title="Login to Manager Interface">
    Log in to Apinizer Manager interface
  </Step>

  <Step title="Go to Portal Tab">
    Click on **Portal** tab in the top menu bar
  </Step>

  <Step title="View Portal List">
    Portal list automatically loads and all portals are displayed
  </Step>
</Steps>

<Frame caption="Portal List Screen">
  <img src="https://mintcdn.com/apinizer/aRrmHEq9-3Zvh-Uy/images/portal/multi-portal-liste.png?fit=max&auto=format&n=aRrmHEq9-3Zvh-Uy&q=85&s=adc6bead30671b9fd62e8023e46a86b7" alt="Portal List Screen" width="1000" height="600" style={{ borderRadius: '0.5rem' }} data-path="images/portal/multi-portal-liste.png" />
</Frame>

## Creating New Portal

Follow the steps below to create a new API Developer Portal:

<Steps>
  <Step title="Access Portal Creation Screen">
    * Click on **Portal** tab in the top menu bar
    * Click **"+ Create New Portal"** button in the top right corner
    * Portal creation form opens
  </Step>

  <Step title="Enter Portal Information">
    Fill in the following information in the opened form window:

    <Accordion title="Name - Required">
      * Enter a unique identifier name for the portal
      * Only letters, numbers, and dash (-) characters can be used
      * Space character cannot be used
      * Example: `partner-portal`, `internal-dev-portal`

      <Warning>This name is used as a technical identifier within the system and cannot be changed later.</Warning>
    </Accordion>

    <Accordion title="Display Name - Required">
      * Name that will appear in portal user interface
      * Turkish and English characters can be used
      * Space character can be used
      * Example: `Partner API Portal`, `Internal Developer Portal`

      <Info>This name appears on portal home page and in email notifications.</Info>
    </Accordion>

    <Accordion title="Visibility Type - Required">
      Select portal access level:

      **Public (Open to Everyone):**

      * Portal is open to everyone
      * Anyone who registers can access the portal
      * Suitable for general use

      **Internal (Internal Use):**

      * Portal is only open to authorized users
      * Requires administrator approval
      * Suitable for corporate internal use
    </Accordion>
  </Step>

  <Step title="Creating Portal">
    * Make sure all required fields are filled
    * Click **"Create"** button
    * System creates the portal and the process is completed
    * Success message is shown and you are redirected to portal list
  </Step>
</Steps>

<Frame caption="New Portal Creation Form">
  <img src="https://mintcdn.com/apinizer/U15B0f1APiqMC1Xa/images/portal/multi-portal-bilgileri-formu.png?fit=max&auto=format&n=U15B0f1APiqMC1Xa&q=85&s=a4f8c09216363f77d434905925e771c9" alt="Portal Information Form" width="1000" height="600" style={{ borderRadius: '0.5rem' }} data-path="images/portal/multi-portal-bilgileri-formu.png" />
</Frame>

<Note>
  After the portal is created, a unique URL is automatically created for the portal. You can customize this URL from portal settings.
</Note>

## Accessing Portal Detail Page

You can use one of the following methods to access the portal detail page:

<Steps>
  <Step title="Method 1: From List">
    * Click on one of the portals displayed in the portal list
    * Portal detail page opens
  </Step>

  <Step title="Method 2: From Action Menu">
    * Click on the three-dot menu on the right of the relevant portal in the portal list
    * Select **"View Details"** or **"Edit"** option
    * Portal detail page opens
  </Step>
</Steps>

## Portal Overview

**Overview (Overview)** tab opens by default on the portal detail page. This page displays all configuration settings and statistics of the portal.

<Frame caption="Portal Overview Screen">
  <img src="https://mintcdn.com/apinizer/U15B0f1APiqMC1Xa/images/portal/multi-portal-overview.png?fit=max&auto=format&n=U15B0f1APiqMC1Xa&q=85&s=8c346bc0bac9c8b94c8b0c69b235a45f" alt="Portal Overview Screen - Multi Portal Selection Menu and Setup Steps" width="1000" height="600" style={{ borderRadius: '0.5rem' }} data-path="images/portal/multi-portal-overview.png" />
</Frame>

### Overview Sections

The Overview page contains the following information cards and sections:

<AccordionGroup>
  <Accordion title="Basic Information" icon="info-circle">
    **Portal Identity Information:**

    * **Portal URL:** Full URL address used to access the portal
    * **Portal ID:** Unique identifier automatically created by the system
    * **Portal Status:** Active or Passive status
    * **Creation Date:** Date and time when the portal was created
    * **Last Update:** Date and time when the portal was last updated

    <Info>You can click the copy icon next to the URL to copy the Portal URL.</Info>
  </Accordion>

  <Accordion title="Security and Access Settings" icon="lock">
    **Security Configurations:**

    * **Account Creation:** Permission for developers to create their own accounts (Active/Passive)
    * **Auto Approval:** Automatic approval of new accounts (Active/Passive)
    * **API Subscription Approval:** Automatic approval for API subscriptions (Active/Passive)
    * **Credential Management:** Permission for users to manage their own API keys (Active/Passive)
    * **Organization Administrator Permissions:** Account management permissions for organization administrators

    <Info>Go to [Portal Settings](/en/api-portal/api-portal-settings) page to change these settings.</Info>
  </Accordion>

  <Accordion title="Language and Localization" icon="globe">
    **Multi-Language Settings:**

    * **Default Language:** Portal's default language (TR/EN)
    * **Turkish Support:** Whether Turkish language option is active
    * **English Support:** Whether English language option is active
    * **Multi-Language Mode:** If both languages are active, multi-language mode is automatically activated

    <Note>When multi-language mode is active, portal content can be displayed in both languages.</Note>
  </Accordion>

  <Accordion title="Active Features" icon="puzzle-piece">
    **Portal Features:**

    * **How to Use Menu:** Whether "How to Use" menu is active
    * **Test Tools (Try It Out):** Whether API test console is active
    * **Jira Integration:** Whether Jira ticket creation feature is active
    * **Analytics:** Whether usage statistics and reporting feature is active
    * **API Documentation:** API documentation viewing feature

    <Info>Use Portal Settings → Features tab to activate/deactivate features.</Info>
  </Accordion>

  <Accordion title="Statistics and Metrics" icon="chart-line">
    **Portal Usage Statistics:**

    * **Published API Count:** Total number of API products published on the portal
    * **Registered Developer Count:** Total number of developer/account registered on the portal
    * **Active Developer Count:** Number of developers in active status
    * **Created Application Count:** Total number of application registrations on the portal
    * **Total API Call Count:** Total number of API calls made through the portal
    * **Last 30 Days Calls:** Number of API calls made in the last 30 days

    <Tip>Statistics are updated in real-time and help you track portal usage.</Tip>
  </Accordion>
</AccordionGroup>

<Info>
  You can be redirected to Portal Settings page by clicking on relevant sections to change settings on the Overview page. You can review the [Portal Settings](/en/api-portal/api-portal-settings) documentation for detailed information.
</Info>

## Portal Editing

Follow the steps below to edit portal information:

<Steps>
  <Step title="Access Portal Detail Page">
    * Click on the portal you want to edit from the portal list
    * Portal detail page opens
  </Step>

  <Step title="Click Edit Button">
    * Click **"Edit"** or **"Configure"** button at the top of the page
    * Alternatively, you can select **"Edit"** option from the three-dot menu on the right of the relevant portal in the portal list
  </Step>

  <Step title="Update Information">
    In the opened edit form, you can update the following information:

    <Accordion title="Display Name">
      * You can change the portal's display name
      * This name appears in portal interface and email notifications
      * Name change is reflected immediately
    </Accordion>

    <Accordion title="Visibility Type">
      * You can change portal access level
      * **Public:** Open to everyone
      * **Internal:** Open only to authorized users

      <Warning>Changing visibility type may affect existing users' access.</Warning>
    </Accordion>

    <Accordion title="Portal URL">
      * You can customize portal URL (if customization permission exists)
      * URL format: `https://your-domain.com/portal-name`

      <Note>When URL is changed, links to the old URL may not work.</Note>
    </Accordion>
  </Step>

  <Step title="Save Changes">
    * Review your changes
    * Click **"Save"** or **"Update"** button
    * Success message is shown and changes are saved
  </Step>
</Steps>

<Note>
  Portal name (Name) is a technical identifier and cannot be changed after creation. Only display name (Display Name) can be updated.
</Note>

## Portal Status Management

You can manage the active or passive status of the portal. A passive portal cannot be accessed by users but is not deleted.

### Making Portal Active/Passive

<Steps>
  <Step title="Access Portal Detail Page">
    * Click on the relevant portal from the portal list
    * Portal detail page opens
  </Step>

  <Step title="Change Status">
    To make portal passive:

    * Click **"Deactivate"** or status toggle button at the top of the page
    * Confirmation dialog opens

    To make portal active again:

    * Click **"Activate"** button
    * Confirmation dialog opens
  </Step>

  <Step title="Confirm">
    * Confirm the operation in the opened confirmation dialog
    * Click **"Yes"** or **"Confirm"** button
    * Portal status is updated
  </Step>
</Steps>

### Effects of Status Change

<Tabs>
  <Tab title="Active Portal">
    **Active Portal Features:**

    * Users can access the portal
    * APIs can be viewed and used
    * New user registrations are accepted
    * Email notifications are sent
    * Analytics data is collected
  </Tab>

  <Tab title="Passive Portal">
    **Passive Portal Features:**

    * Users cannot access the portal (they get 404 error)
    * Existing sessions are terminated
    * New user registrations are not accepted
    * Email notifications are not sent
    * Analytics data is not collected
    * Portal settings and content are preserved (not deleted)

    <Warning>Making portal passive immediately cuts access of existing users. Do this carefully.</Warning>
  </Tab>
</Tabs>

## Portal Deletion

Follow the steps below to permanently delete the portal:

<Warning>
  Portal deletion operation cannot be undone. The deleted portal and all its data (users, APIs, content, statistics) are permanently deleted.
</Warning>

<Steps>
  <Step title="Access Portal Detail Page">
    * Click on the portal you want to delete from the portal list
    * Portal detail page opens
  </Step>

  <Step title="Go to Danger Zone Section">
    * Click on **"Danger Zone"** tab at the bottom of the page
    * Critical operations are located in this section
  </Step>

  <Step title="Click Deletion Button">
    * Click **"Delete Portal"** or **"Remove Portal"** button
    * Confirmation dialog opens
  </Step>

  <Step title="Confirm Portal Name">
    * You are asked to enter the portal name in the confirmation dialog
    * Enter the portal name exactly (case sensitive)
    * This step is to prevent accidental deletion
  </Step>

  <Step title="Confirm Deletion Operation">
    * Make sure you entered the portal name correctly
    * Click **"Yes, Delete"** or **"Confirm Delete"** button
    * Portal is permanently deleted
    * You are redirected to portal list
  </Step>
</Steps>

### Effects of Deletion Operation

When portal is deleted, the following data is permanently deleted:

| Data Type                     | Description                                     |
| ----------------------------- | ----------------------------------------------- |
| **Portal Configuration**      | All portal settings and configurations          |
| **User Accounts**             | All developer accounts registered on the portal |
| **API Products**              | All API products published on the portal        |
| **Application Registrations** | All application registrations and subscriptions |
| **API Keys**                  | All created API keys (Client ID/Secret)         |
| **Content**                   | Portal content, documentation pages             |
| **Statistics**                | All analytics data and usage statistics         |
| **Files**                     | All files uploaded on the portal                |

<Info>
  It is recommended to take time to backup important data or move to a different portal before deleting the portal.
</Info>

## Portal Management

After creating the portal, you can perform the following management operations:

<CardGroup cols={3}>
  <Card title="Theme Customization" icon="paintbrush" href="/en/api-portal/appearance-theme">
    Customize portal appearance and theme
  </Card>

  <Card title="API Management" icon="code" href="/en/api-portal/api-product">
    Manage APIs to be published on the portal
  </Card>

  <Card title="User Management" icon="user-gear" href="/en/api-portal/accounts-developers">
    Manage developer accounts and permissions
  </Card>

  <Card title="Content Management" icon="file-lines" href="/en/api-portal/api-portal-settings">
    Edit portal content
  </Card>

  <Card title="Security Settings" icon="shield" href="/en/api-portal/api-portal-settings">
    Configure access control and security policies
  </Card>

  <Card title="Analytics" icon="chart-bar" href="/en/api-portal/api-portal-settings">
    View portal usage statistics
  </Card>
</CardGroup>

## Configuring Portal Settings

After creating the portal, you need to configure basic settings for the portal to work properly.

### Accessing Portal Settings

<Steps>
  <Step title="Go to Portal Detail Page">
    * Click on the relevant portal from the portal list
    * Portal detail page opens
  </Step>

  <Step title="Go to Settings Tab">
    * Click on **"Settings"** or **"Configuration"** tab at the top of the page
    * Alternatively, you can access settings by clicking on relevant sections on the Overview page
  </Step>
</Steps>

### Basic Settings

Portal settings are organized in the following categories:

<AccordionGroup>
  <Accordion title="General Settings">
    **Portal Basic Information:**

    * Portal name and display name
    * Portal URL configuration
    * Default language setting
    * Multi-language support (TR/EN)
    * Portal description

    <Info>Review [Portal Settings - General](/en/api-portal/api-portal-settings#general-settings) section for detailed information.</Info>
  </Accordion>

  <Accordion title="Email Settings">
    **Email Configuration:**

    * Email server settings
    * Sender email address
    * Email templates (registration, approval, password reset, etc.)
    * Email notification settings

    <Info>Review [Portal Settings - Email](/en/api-portal/api-portal-settings#email-notifications) section for detailed information.</Info>
  </Accordion>

  <Accordion title="Security Settings">
    **Security Configurations:**

    * Account creation permissions
    * Auto approval settings
    * API subscription approval processes
    * Credential management permissions
    * Organization administrator permissions

    <Info>Review [Portal Settings - Security](/en/api-portal/api-portal-settings#security) section for detailed information.</Info>
  </Accordion>

  <Accordion title="Feature Settings">
    **Portal Features:**

    * How to Use menu
    * Test tools (Try It Out)
    * Jira integration
    * Analytics feature
    * Performance metrics

    <Info>Review [Portal Settings - Features](/en/api-portal/api-portal-settings#features) section for detailed information.</Info>
  </Accordion>

  <Accordion title="Legal Settings">
    **Legal Regulations:**

    * Terms of Service
    * Privacy Policy
    * Legal file upload

    <Info>Review [Portal Settings - Legal](/en/api-portal/api-portal-settings#legal) section for detailed information.</Info>
  </Accordion>
</AccordionGroup>

<Note>
  After changing portal settings, make sure to click the **"Save"** button to save changes. Unsaved changes will be lost.
</Note>

## Portal Access and URL Management

### Accessing Portal URL

A unique URL is automatically created for each portal. You can access the portal using this URL.

<Steps>
  <Step title="Find Portal URL">
    * Go to Overview tab on portal detail page
    * Full URL address is displayed in **"Portal URL"** section
    * You can copy the URL by clicking the copy icon next to the URL
  </Step>

  <Step title="Access Portal">
    * Paste the copied URL into browser address bar
    * Press Enter
    * Portal home page opens
  </Step>
</Steps>

### Portal URL Format

Portal URLs are created in the following format:

```
https://your-domain.com/portal/{portal-name}
```

**Example:**

* Portal name: `partner-portal`
* Portal URL: `https://api.company.com/portal/partner-portal`

<Info>
  You can use the **"Custom Portal URL"** field from Portal Settings → General Settings section to customize portal URL.
</Info>

### Portal Access Control

Portal access is controlled according to the portal's visibility type:

<Tabs>
  <Tab title="Public Portal">
    **Open to Everyone Portal:**

    * Everyone can access the portal
    * Can click "Sign Up" button to register
    * Portal home page and API catalog are open to everyone
    * Can view APIs but needs to register to use them
  </Tab>

  <Tab title="Internal Portal">
    **Internal Use Portal:**

    * Only authorized users can access
    * Users must be added manually by administrator
    * Registration button is not visible or disabled
    * Portal content is only shown to logged in users
  </Tab>
</Tabs>

### Administrator Permissions

Portal administrators can perform the following operations:

| Permission              | Description                              |
| ----------------------- | ---------------------------------------- |
| **Portal Settings**     | View and edit portal general settings    |
| **User Management**     | View, approve, reject developer accounts |
| **API Management**      | View, publish, unpublish API products    |
| **Content Management**  | Edit portal content, add documentation   |
| **Analytics**           | View portal usage statistics             |
| **Theme Customization** | Customize portal appearance and theme    |

<Warning>
  Portal administrators cannot delete the portal or remove other administrators. These operations can only be performed by system administrators.
</Warning>

## Next Steps

After completing portal creation and basic configuration operations:

<Steps>
  <Step title="Configure Portal Settings">
    * Configure general settings (language, URL, email)
    * Determine security settings (account creation, auto approval)
    * Activate feature settings (Try It, Analytics, Jira)
    * Upload legal files (Terms of Service, Privacy Policy)
  </Step>

  <Step title="Customize Portal Appearance">
    * Set logo and color scheme
    * Prepare home page content
    * Customize portal theme
  </Step>

  <Step title="Publish APIs">
    * Create API products to be published on the portal
    * Prepare API documentation
    * Configure pricing plans
    * Publish APIs (Publish)
  </Step>

  <Step title="Configure User Management">
    * Assign portal administrators
    * Create developer accounts or start registration process
    * Determine user roles and permissions
  </Step>

  <Step title="Prepare Content">
    * Prepare portal home page content
    * Create documentation pages
    * Edit "How to Use" page
    * Add help and support content
  </Step>

  <Step title="Test Portal">
    * Log in to portal with different user roles
    * Test APIs
    * Check email notifications
    * Make sure all features are working
  </Step>

  <Step title="Publish Portal">
    * After completing all configurations, activate the portal
    * Share portal URL with users
    * Invite developers to the portal
  </Step>
</Steps>

## Frequently Asked Questions

<Accordion title="Can I create multiple portals?">
  Yes, you can create as many portals as you want. Each portal works completely independently and has its own settings, users, and APIs.

  **Usage Scenarios:**

  * Separate portals for different departments
  * Special portals for partner companies
  * Separate portals for test and production environments
  * Localized portals for different regions
</Accordion>

<Accordion title="Can I change the portal name after creation?">
  Portal name (Name) is a technical identifier and cannot be changed after creation. However, display name (Display Name) can be changed at any time.

  **Can be Changed:**

  * Display Name
  * Portal URL (if customization permission exists)
  * Portal description

  **Cannot be Changed:**

  * Portal name (Name) - technical identifier
</Accordion>

<Accordion title="Can I reactivate a passive portal?">
  Yes, you can reactivate a passive portal at any time. When portal is made passive:

  * All settings and content are preserved
  * User accounts are not deleted
  * APIs and documentation are preserved
  * Portal works as before when reactivated
</Accordion>

<Accordion title="Can portal data be recovered after deletion?">
  No, portal deletion operation cannot be undone. The deleted portal and all its data (users, APIs, content, statistics) are permanently deleted.

  **Recommendations:**

  * Backup important data before deleting portal
  * Temporarily disable by making portal passive
  * Evaluate all effects before performing deletion operation
</Accordion>

<Accordion title="Can I copy a portal to another portal?">
  Currently, portal copying feature is not available. However, you can create a similar portal using the following methods:

  **Manual Copying:**

  1. Create a new portal
  2. Manually configure settings
  3. Publish APIs again
  4. Copy content

  <Info>Portal copying feature may be added in future versions.</Info>
</Accordion>

<Accordion title="Can I customize portal URL?">
  Yes, you can customize portal URL. You can specify a custom URL using the **"Custom Portal URL"** field from Portal Settings → General Settings section.

  **Important Notes:**

  * Links to old URL may not work when URL is changed
  * URL format must be in valid domain format
  * URL change may also require DNS settings
</Accordion>

<Accordion title="What can users assigned as portal administrators do?">
  Portal administrators can perform the following operations:

  **What They Can Do:**

  * View and edit portal settings
  * Manage user accounts (approve, reject)
  * Manage API products (publish, unpublish)
  * Edit portal content
  * View analytics data
  * Theme customization

  **What They Cannot Do:**

  * Delete portal
  * Remove other administrators
  * Change system-level settings
</Accordion>

<Accordion title="What is the difference between Public and Internal portal?">
  **Public Portal (Open to Everyone):**

  * Everyone can access the portal
  * Registration button is visible
  * Anyone can register (with automatic or manual approval)
  * Suitable for general use

  **Internal Portal (Internal Use):**

  * Only authorized users can access
  * Registration button is not visible or disabled
  * Users are added manually by administrator
  * Suitable for corporate internal use
</Accordion>

<Tip>
  Since each portal works completely independently, you can create separate portals for different departments or projects to provide isolated environments. This way, each portal can be managed independently with its own users, APIs, and content.
</Tip>