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
Log in as platform admin
Navigate to Admin → Organizations
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:
Click on an application to view details
Review the information provided:
Company legal information
Representative credentials
Business description
Intended asset classes
Legal documentation (if uploaded)
Verify legitimacy:
Cross-reference company registration number
Verify representative identity
Check legal jurisdiction validity
Review website and business presence
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:
Navigate to Admin → Organizations
Click Organizations tab
Click Create Organization button
Fill in required information:
Company name
Legal structure
Registration number
Legal jurisdiction
Contact email
Phone number
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:
Click on an organization in the list
Click Edit button
Modify any field as needed
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:
Navigate to organization detail
Click Suspend button
Provide suspension reason
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:
Navigate to Admin → Organizations
Click on an organization
Click Assign Admin button (or navigate to admin assignment section)
Search for user by email
Select user from results
Add optional notes about the assignment
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:
Find the admin in the list
Click Revoke button
Provide revocation reason
Confirm revocation
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
Navigate to Admin → Projects
Filter by status: Submitted or Under Review
Click on a project to view details
Project Review Checklist
When reviewing a project, verify:
Legal & Compliance:
Financial Information:
Project Details:
Media & Documentation:
Token Classes:
Making a Decision
Option 1: Approve the Project
Click Approve button
Add approval notes (optional)
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
Click Request Revisions button
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.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
Click Reject button
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.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
Navigate to Admin → Organizations
Click Change Requests tab
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:
Click Approve button
Add admin notes (optional):
Change approved. Certificate of Amendment verified with [State] Secretary of State. File number: [123456]. Company name officially changed on [date].Confirm approval
Result:
Organization field is automatically updated
Change request status: "approved"
Issuer receives approval notification
Change is logged in audit trail
To Reject:
Click Reject button
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.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
Navigate to Admin → Security
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:
Navigate to Admin → Audit Logs
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:
Investigate: Review audit logs for the user/entity
Assess: Determine severity and scope
Act: Suspend account if necessary
Document: Record incident details
Notify: Contact affected parties if needed
7.8 Platform Settings Management
Platform admins can configure global platform settings:
Navigate to Admin → Settings
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
Last updated
Was this helpful?