# Platform Admin Functions

#### 7.1 Overview of Platform Admin Responsibilities

Platform admins are the gatekeepers and managers of the entire Treem platform. They ensure regulatory compliance, verify organization legitimacy, and approve projects before they go live to investors.

**Core Functions:**

* Issuer application review and approval
* Organization creation and management
* Issuer admin assignment
* Project review and approval
* Organization change request review
* Platform security monitoring
* Audit log access
* System settings management

#### 7.2 Managing Issuer Applications

**Accessing Applications**

1. Log in as platform admin
2. Navigate to **Admin → Organizations**
3. Click on **Applications** tab

**Application List View**

The applications table shows:

* Company name
* Representative name and email
* Application status (Pending, Approved, Rejected)
* Submission date
* Action buttons

**Reviewing an Application**

**Step-by-Step Review Process:**

1. **Click on an application** to view details
2. **Review the information provided:**
   * Company legal information
   * Representative credentials
   * Business description
   * Intended asset classes
   * Legal documentation (if uploaded)
3. **Verify legitimacy:**
   * Cross-reference company registration number
   * Verify representative identity
   * Check legal jurisdiction validity
   * Review website and business presence
4. **Make a decision:**

   **To Approve:**

   * Click **Approve** button
   * Add admin notes (optional but recommended)
   * System automatically creates organization
   * Applicant receives approval notification

   **To Reject:**

   * Click **Reject** button
   * Add admin notes explaining rejection reason (required)
   * Applicant receives rejection notification
   * Application cannot be re-opened (must submit new)

**What Happens After Approval:**

* A new organization is automatically created
* Organization inherits data from application
* Company name and address are automatically locked
* Application status changes to "Approved"
* Applicant can now log in and access issuer console
* No issuer admin is assigned yet (must be done separately)

**Admin Notes Best Practices:**

**For Approvals:**

```
Application approved. Company verified through [source]. 
Registration number confirmed with [jurisdiction authority].
Cleared for real estate tokenization projects.
```

**For Rejections:**

```
Application rejected. Reasons:
1. Unable to verify company registration number
2. Representative email domain does not match company website
3. Insufficient information about intended projects
Applicant may reapply with corrected information.
```

#### 7.3 Creating & Managing Organizations

**Creating Organizations Manually**

While most organizations are created through application approval, admins can create organizations directly:

1. Navigate to **Admin → Organizations**
2. Click **Organizations** tab
3. Click **Create Organization** button
4. Fill in required information:
   * Company name
   * Legal structure
   * Registration number
   * Legal jurisdiction
   * Contact email
   * Phone number
5. Click **Create**

**When to Create Manually:**

* Onboarding enterprise clients
* Migrating existing issuers to platform
* Testing purposes
* Special partnerships

**Viewing All Organizations**

The Organizations tab displays:

* Company name
* Contact information
* Number of assigned admins
* Creation date
* Status (Active, Suspended)
* Action buttons

**Editing Organizations**

**Platform admins can edit any field**, including locked fields:

1. Click on an organization in the list
2. Click **Edit** button
3. Modify any field as needed
4. Click **Save**

**Editable Fields (including locked):**

* Company name\*
* Company address\*
* Contact information
* Legal details
* Logo
* Description
* Platform locked fields configuration

\*Note: Direct edits by platform admin do not require change requests. Only issuer admins must submit change requests for locked fields.

**Suspending Organizations**

If an organization violates terms or requires investigation:

1. Navigate to organization detail
2. Click **Suspend** button
3. Provide suspension reason
4. Confirm suspension

**Effects of Suspension:**

* Issuer admins cannot log in
* All projects become unavailable to investors
* Existing investments are frozen
* Organization appears in "Suspended" status

**To Reactivate:**

* Click **Reactivate** button
* Provide reactivation notes
* All projects resume normal status

#### 7.4 Assigning Issuer Admins

Organizations require at least one issuer admin to operate. Platform admins assign users as issuer admins.

**How to Assign an Issuer Admin:**

1. Navigate to **Admin → Organizations**
2. Click on an organization
3. Click **Assign Admin** button (or navigate to admin assignment section)
4. **Search for user** by email
5. **Select user** from results
6. Add optional notes about the assignment
7. Click **Assign**

**Prerequisites:**

* User must already exist in the system
* User must have verified email
* User should not be another organization's admin (unless multi-org)

**Managing Existing Admins:**

View assigned admins:

* Issuer admin name and email
* Assignment date
* Assigned by (which platform admin)
* Status (Active, Revoked)

**To Revoke an Admin:**

1. Find the admin in the list
2. Click **Revoke** button
3. Provide revocation reason
4. Confirm revocation
5. User loses access to organization immediately

**Audit Trail:**

* All admin assignments are logged
* Revocations are tracked with reasons
* Assignment history is permanent

#### 7.5 Project Review & Approval

**Accessing Submitted Projects**

1. Navigate to **Admin → Projects**
2. Filter by status: **Submitted** or **Under Review**
3. Click on a project to view details

**Project Review Checklist**

When reviewing a project, verify:

**Legal & Compliance:**

* [ ] Offering type is appropriate for jurisdiction
* [ ] Legal disclaimers are complete
* [ ] KYC/AML procedures are in place
* [ ] Jurisdiction is clearly stated
* [ ] Issuer entity is properly formed

**Financial Information:**

* [ ] All calculations are accurate
* [ ] Target amount is reasonable
* [ ] Token pricing makes sense
* [ ] Projected returns are realistic (not exaggerated)
* [ ] Use of funds totals 100%
* [ ] Financial metrics (IRR, cap rate) are credible

**Project Details:**

* [ ] Description is clear and comprehensive
* [ ] Property/asset actually exists
* [ ] Location is accurate
* [ ] Key highlights are factual
* [ ] Exit strategy is reasonable

**Media & Documentation:**

* [ ] Hero image is professional quality
* [ ] Gallery images are relevant
* [ ] Documents are uploaded (offering memo, etc.)
* [ ] No copyrighted content without permission

**Token Classes:**

* [ ] Token terms are clear
* [ ] Pricing is appropriate
* [ ] Min/max investment ranges are logical
* [ ] Rights and restrictions are well-defined

**Making a Decision**

**Option 1: Approve the Project**

1. Click **Approve** button
2. Add approval notes (optional)
3. Confirm approval

**Result:**

* Project status changes to "approved"
* Project becomes visible to all investors
* Issuer receives approval notification
* Project appears in marketplace

**Option 2: Request Revisions**

1. Click **Request Revisions** button
2. **Provide detailed feedback** (required):

   ```
   Please address the following items before resubmission:

   1. Financial Metrics: The projected IRR of 45% seems unrealistic 
      for this asset class. Please provide supporting analysis or 
      adjust to industry standards (8-12% for similar properties).

   2. Documentation: Please upload the independent property appraisal 
      report mentioned in the description.

   3. Token Class: Class A voting rights description is unclear. 
      Please specify exactly what decisions token holders can vote on.

   4. Images: Gallery image #3 appears to be from a different property. 
      Please replace with actual project photos.
   ```
3. Confirm request

**Result:**

* Project status changes to "revision\_requested"
* Project returns to issuer as draft
* Issuer can make changes and resubmit
* Your feedback is visible to issuer

**Option 3: Reject the Project**

1. Click **Reject** button
2. Provide detailed rejection reasons:

   ```
   Project rejected for the following reasons:

   1. The property does not meet platform standards for 
      institutional-quality assets.

   2. Financial projections appear to be misleading or unsubstantiated.

   3. Legal structure does not comply with Reg D requirements.

   Issuer may submit a different project or reapply with significant 
   changes to this offering.
   ```
3. Confirm rejection

**Result:**

* Project status changes to "rejected"
* Project cannot be edited or resubmitted
* Issuer can view rejection reason
* Issuer must create new project if desired

**Review Timeline Best Practices**

* **Acknowledge receipt**: Within 1 business day
* **Initial review**: Within 3 business days
* **Final decision**: Within 7 business days
* **Expedited review**: Available for pre-vetted issuers

#### 7.6 Organization Change Request Review

**Accessing Change Requests**

1. Navigate to **Admin → Organizations**
2. Click **Change Requests** tab
3. View pending requests

**Change Request Details**

Each request shows:

* Organization name
* Field to be changed (Company Name or Company Address)
* Current value
* Requested new value
* Supporting documentation link
* Requested by (issuer admin name)
* Request date

**Reviewing a Change Request**

**Step 1: Review Documentation**

* Click on supporting document link
* Verify legitimacy of documentation
* Common documents include:
  * Certificate of Amendment
  * Board Resolution
  * Updated Articles of Incorporation
  * Government registration documents
  * Legal opinion letter

**Step 2: Verify the Change**

* Cross-reference with government databases
* Verify signatures and notarization
* Ensure documentation is recent
* Check consistency across documents

**Step 3: Make a Decision**

**To Approve:**

1. Click **Approve** button
2. Add admin notes (optional):

   ```
   Change approved. Certificate of Amendment verified with 
   [State] Secretary of State. File number: [123456].
   Company name officially changed on [date].
   ```
3. Confirm approval

**Result:**

* Organization field is automatically updated
* Change request status: "approved"
* Issuer receives approval notification
* Change is logged in audit trail

**To Reject:**

1. Click **Reject** button
2. Add admin notes (required):

   ```
   Change request rejected. Reasons:

   1. Submitted Certificate of Amendment appears to be incomplete 
      (missing page 2).

   2. Document is not notarized as required by [State] law.

   3. Company name requested is already in use by another entity 
      in our system.

   Please resubmit with complete, notarized documentation.
   ```
3. Confirm rejection

**Result:**

* Organization field remains unchanged
* Change request status: "rejected"
* Issuer can view rejection reason
* Issuer may submit a new change request

**Change Request Best Practices**

**For Company Name Changes:**

* Verify with state/country business registry
* Check for trademark conflicts
* Ensure consistency across all legal documents
* Update all related project materials

**For Address Changes:**

* Verify new address is legitimate business location
* Confirm address with utility or lease documentation
* Update any regulatory filings
* Ensure compliance with jurisdiction requirements

#### 7.7 Platform Security Monitoring

**Accessing Security Dashboard**

1. Navigate to **Admin → Security**
2. View security monitoring panels

**Key Metrics Displayed:**

* Failed login attempts
* Suspicious activity alerts
* API rate limit violations
* Unusual access patterns
* Data export events

**Audit Log Access**

View comprehensive audit logs:

1. Navigate to **Admin → Audit Logs**
2. Filter by:
   * Date range
   * User
   * Event type
   * Entity type
   * Action

**Logged Events Include:**

* User authentication events
* Role assignments
* Project submissions/approvals
* Organization changes
* Change request actions
* Admin actions
* Data access (sensitive information)

**Audit Log Details:**

* Timestamp
* User who performed action
* Action type
* Entity affected
* IP address
* User agent
* Event details (JSON)

**Responding to Security Incidents**

If suspicious activity is detected:

1. **Investigate**: Review audit logs for the user/entity
2. **Assess**: Determine severity and scope
3. **Act**: Suspend account if necessary
4. **Document**: Record incident details
5. **Notify**: Contact affected parties if needed

#### 7.8 Platform Settings Management

Platform admins can configure global platform settings:

1. Navigate to **Admin → Settings**
2. Modify settings as needed

**Configurable Settings:**

* Minimum investment thresholds
* KYC/AML requirements
* Investor accreditation requirements
* Document retention policies
* Fee structures
* Email notification templates
* Platform branding
* Feature flags

***