# About WRLD Tech Co.
Source: https://help.wrld.tech/about
Mission, vision, and values of WRLD Tech Co. (WRLD Inc.)
## Who we are
**WRLD Tech Co.** (legally WRLD Inc., operating as WRLD.Tech) is a business technology consultancy founded by a team with a diverse background in computer science, software development, UI/UX design, management information systems, cloud development, and infrastructure. The company was named after the initials of the founders, and since its inception it has been committed to giving clients the most proficient technology-focused solutions to expedite and streamline their growth.
We're a true one-stop-shop for small and mid-size businesses: anything with a screen or that "speaks in 0s and 1s" is something we can help with, from on-site networking, security, IT systems and VoIP, up through web development, marketing systems, and CRM consultation. Rather than wearing every hat ourselves, we optimize and integrate a network of partner pros — leveraging our own server infrastructure across nearly every engagement and referring specialized work to trusted partners when that is the right move.
We are based in Dallas, TX with representatives and clients in Austin, TX and Denver, CO. Our office is at 4707 Algiers St. Ste 101, Dallas TX 75207, with official hours of 10am–6pm Monday–Friday (and typically flexible outside of them).
## Mission
At WRLD.Tech, our mission is to provide our clients with the most proficient technology-focused solutions to expedite and streamline their growth.
## Vision
Our vision is to be the leading technology partner for businesses looking to leverage the latest technology tools and services to unlock new levels of productivity, efficiency, and growth.
## Values
Our clients entrust us with their security, infrastructure, and operational efficiency. When things go wrong we're on top of it; when we slow down or miss a deadline, it matters.
We stay at the forefront of technology, constantly exploring new tools and approaches that improve our clients' businesses.
Integrity is the foundation of every relationship. We operate with transparency, put clients' best interests first, and hold ourselves to the highest ethical standards.
We strive for excellence in everything we do and deliver top-notch service and solutions.
We work closely with clients to understand unique needs and provide tailored solutions, with open communication and feedback throughout.
We are humble and approachable, take ownership proactively, and value feedback to constantly improve and exceed expectations.
## Our promise
* Consistent, reliable service
* Honesty and candor
* Goal alignment with your business
* Competitive rates and a referral-friendly ethos
* Satisfaction guaranteed
* Your success is our success
## What makes us different
WRLD.Tech is a tight team of technology experts with decades of combined experience in software development, UI/UX design, management information systems, cloud development, and infrastructure. We optimize for outcomes: integrating our own infrastructure (WRLD.host), our AI tooling (WRLD.ai), and a trusted partner network so you don't have to assemble and manage vendors yourself.
Email, ticket, or call the help desk.
Book time with the WRLD team.
# Claude Code setup
Source: https://help.wrld.tech/ai-tools/claude-code
Configure Claude Code for your documentation workflow
Claude Code is Anthropic's official CLI tool. This guide will help you set up Claude Code to help you write and maintain your documentation.
## Prerequisites
* Active Claude subscription (Pro, Max, or API access)
## Setup
1. Install Claude Code globally:
```bash theme={null}
npm install -g @anthropic-ai/claude-code
```
2. Navigate to your docs directory.
3. (Optional) Add the `CLAUDE.md` file below to your project.
4. Run `claude` to start.
## Create `CLAUDE.md`
Create a `CLAUDE.md` file at the root of your documentation repository to train Claude Code on your specific documentation standards:
```markdown theme={null}
# Mintlify documentation
## Working relationship
- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
- ALWAYS ask for clarification rather than making assumptions
- NEVER lie, guess, or make up information
## Project context
- Format: MDX files with YAML frontmatter
- Config: docs.json for navigation, theme, settings
- Components: Mintlify components
## Content strategy
- Document just enough for user success - not too much, not too little
- Prioritize accuracy and usability of information
- Make content evergreen when possible
- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
- Check existing patterns for consistency
- Start by making the smallest reasonable changes
## Frontmatter requirements for pages
- title: Clear, descriptive page title
- description: Concise summary for SEO/navigation
## Writing standards
- Second-person voice ("you")
- Prerequisites at start of procedural content
- Test all code examples before publishing
- Match style and formatting of existing pages
- Include both basic and advanced use cases
- Language tags on all code blocks
- Alt text on all images
- Relative paths for internal links
## Git workflow
- NEVER use --no-verify when committing
- Ask how to handle uncommitted changes before starting
- Create a new branch when no clear branch exists for changes
- Commit frequently throughout development
- NEVER skip or disable pre-commit hooks
## Do not
- Skip frontmatter on any MDX file
- Use absolute URLs for internal links
- Include untested code examples
- Make assumptions - always ask for clarification
```
# Cursor setup
Source: https://help.wrld.tech/ai-tools/cursor
Configure Cursor for your documentation workflow
Use Cursor to help write and maintain your documentation. This guide shows how to configure Cursor for better results on technical writing tasks and using Mintlify components.
## Prerequisites
* Cursor editor installed
* Access to your documentation repository
## Project rules
Create project rules that all team members can use. In your documentation repository root:
```bash theme={null}
mkdir -p .cursor
```
Create `.cursor/rules.md`:
````markdown theme={null}
# Mintlify technical writing rule
You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
## Core writing principles
### Language and style requirements
- Use clear, direct language appropriate for technical audiences
- Write in second person ("you") for instructions and procedures
- Use active voice over passive voice
- Employ present tense for current states, future tense for outcomes
- Avoid jargon unless necessary and define terms when first used
- Maintain consistent terminology throughout all documentation
- Keep sentences concise while providing necessary context
- Use parallel structure in lists, headings, and procedures
### Content organization standards
- Lead with the most important information (inverted pyramid structure)
- Use progressive disclosure: basic concepts before advanced ones
- Break complex procedures into numbered steps
- Include prerequisites and context before instructions
- Provide expected outcomes for each major step
- Use descriptive, keyword-rich headings for navigation and SEO
- Group related information logically with clear section breaks
### User-centered approach
- Focus on user goals and outcomes rather than system features
- Anticipate common questions and address them proactively
- Include troubleshooting for likely failure points
- Write for scannability with clear headings, lists, and white space
- Include verification steps to confirm success
## Mintlify component reference
### Callout components
#### Note - Additional helpful information
Supplementary information that supports the main content without interrupting flow
#### Tip - Best practices and pro tips
Expert advice, shortcuts, or best practices that enhance user success
#### Warning - Important cautions
Critical information about potential issues, breaking changes, or destructive actions
#### Info - Neutral contextual information
Background information, context, or neutral announcements
#### Check - Success confirmations
Positive confirmations, successful completions, or achievement indicators
### Code components
#### Single code block
Example of a single code block:
```javascript config.js
const apiConfig = {
baseURL: 'https://api.example.com',
timeout: 5000,
headers: {
'Authorization': `Bearer ${process.env.API_TOKEN}`
}
};
```
#### Code group with multiple languages
Example of a code group:
```javascript Node.js
const response = await fetch('/api/endpoint', {
headers: { Authorization: `Bearer ${apiKey}` }
});
```
```python Python
import requests
response = requests.get('/api/endpoint',
headers={'Authorization': f'Bearer {api_key}'})
```
```curl cURL
curl -X GET '/api/endpoint' \
-H 'Authorization: Bearer YOUR_API_KEY'
```
#### Request/response examples
Example of request/response documentation:
```bash cURL
curl -X POST 'https://api.example.com/users' \
-H 'Content-Type: application/json' \
-d '{"name": "John Doe", "email": "john@example.com"}'
```
```json Success
{
"id": "user_123",
"name": "John Doe",
"email": "john@example.com",
"created_at": "2024-01-15T10:30:00Z"
}
```
### Structural components
#### Steps for procedures
Example of step-by-step instructions:
Run `npm install` to install required packages.
Verify installation by running `npm list`.
Create a `.env` file with your API credentials.
```bash
API_KEY=your_api_key_here
```
Never commit API keys to version control.
#### Tabs for alternative content
Example of tabbed content:
```bash
brew install node
npm install -g package-name
```
```powershell
choco install nodejs
npm install -g package-name
```
```bash
sudo apt install nodejs npm
npm install -g package-name
```
#### Accordions for collapsible content
Example of accordion groups:
- **Firewall blocking**: Ensure ports 80 and 443 are open
- **Proxy configuration**: Set HTTP_PROXY environment variable
- **DNS resolution**: Try using 8.8.8.8 as DNS server
```javascript
const config = {
performance: { cache: true, timeout: 30000 },
security: { encryption: 'AES-256' }
};
```
### Cards and columns for emphasizing information
Example of cards and card groups:
Complete walkthrough from installation to your first API call in under 10 minutes.
Learn how to authenticate requests using API keys or JWT tokens.
Understand rate limits and best practices for high-volume usage.
### API documentation components
#### Parameter fields
Example of parameter documentation:
Unique identifier for the user. Must be a valid UUID v4 format.
User's email address. Must be valid and unique within the system.
Maximum number of results to return. Range: 1-100.
Bearer token for API authentication. Format: `Bearer YOUR_API_KEY`
#### Response fields
Example of response field documentation:
Unique identifier assigned to the newly created user.
ISO 8601 formatted timestamp of when the user was created.
List of permission strings assigned to this user.
#### Expandable nested fields
Example of nested field documentation:
Complete user object with all associated data.
User profile information including personal details.
User's first name as entered during registration.
URL to user's profile picture. Returns null if no avatar is set.
### Media and advanced components
#### Frames for images
Wrap all images in frames:
#### Videos
Use the HTML video element for self-hosted video content:
Embed YouTube videos using iframe elements:
#### Tooltips
Example of tooltip usage:
API
#### Updates
Use updates for changelogs:
## New features
- Added bulk user import functionality
- Improved error messages with actionable suggestions
## Bug fixes
- Fixed pagination issue with large datasets
- Resolved authentication timeout problems
## Required page structure
Every documentation page must begin with YAML frontmatter:
```yaml
---
title: "Clear, specific, keyword-rich title"
description: "Concise description explaining page purpose and value"
---
```
## Content quality standards
### Code examples requirements
- Always include complete, runnable examples that users can copy and execute
- Show proper error handling and edge case management
- Use realistic data instead of placeholder values
- Include expected outputs and results for verification
- Test all code examples thoroughly before publishing
- Specify language and include filename when relevant
- Add explanatory comments for complex logic
- Never include real API keys or secrets in code examples
### API documentation requirements
- Document all parameters including optional ones with clear descriptions
- Show both success and error response examples with realistic data
- Include rate limiting information with specific limits
- Provide authentication examples showing proper format
- Explain all HTTP status codes and error handling
- Cover complete request/response cycles
### Accessibility requirements
- Include descriptive alt text for all images and diagrams
- Use specific, actionable link text instead of "click here"
- Ensure proper heading hierarchy starting with H2
- Provide keyboard navigation considerations
- Use sufficient color contrast in examples and visuals
- Structure content for easy scanning with headers and lists
## Component selection logic
- Use **Steps** for procedures and sequential instructions
- Use **Tabs** for platform-specific content or alternative approaches
- Use **CodeGroup** when showing the same concept in multiple programming languages
- Use **Accordions** for progressive disclosure of information
- Use **RequestExample/ResponseExample** specifically for API endpoint documentation
- Use **ParamField** for API parameters, **ResponseField** for API responses
- Use **Expandable** for nested object properties or hierarchical information
````
# Warp setup
Source: https://help.wrld.tech/ai-tools/warp
Configure Warp and Oz Agent Skills for your documentation workflow
Warp is an agentic development environment with a built-in AI agent called Oz. This guide shows how to configure Warp for your Mintlify documentation projects using Agent Skills.
## Prerequisites
* Warp terminal installed ([warp.dev](https://warp.dev))
* Access to your documentation repository
## Agent Skills
Agent Skills are markdown files that teach Oz about your conventions, workflows, and best practices. Warp agents automatically discover and use skills placed in `.agents/skills/` directories.
Each skill is a folder containing a `SKILL.md` file with YAML frontmatter and markdown instructions:
```
.agents/skills/
└── your-skill-name/
└── SKILL.md
```
Skills can live in two locations:
* **Project-level**: `.agents/skills/` in your repository root (shared with your team)
* **Global**: `~/.agents/skills/` on your machine (available across all projects)
## Pre-built skills
WRLD maintains a catalog of reusable skills in the [oz-skills](https://github.com/wrldinc/oz-skills) repository. To use one:
1. Copy the skill folder from `.agents/skills/` in the repository.
2. Paste it into your project's `.agents/skills/` directory (or `~/.agents/skills/` for global use).
3. Warp will automatically detect the skill on your next interaction.
Available skills include:
* **docs-update** — Review code changes and update user-facing documentation automatically
* **ci-fix** — Diagnose and fix CI pipeline failures
* **create-pull-request** — Generate well-structured pull requests from code changes
* **seo-aeo-audit** — Audit pages for SEO and AI search engine optimization
* **web-accessibility-audit** — Check sites against WCAG accessibility criteria
* **web-performance-audit** — Analyze and improve web performance metrics
* **mcp-builder** — Build Model Context Protocol servers
* **terraform-style-check** — Enforce Terraform style and best practices
* **webapp-testing** — Automate web application testing workflows
* **github-bug-report-triage** — Triage incoming GitHub bug reports
* **github-issue-dedupe** — Identify and manage duplicate GitHub issues
* **slack-qa-investigate** — Investigate questions from Slack channels
* **scheduler** — Schedule and manage recurring agent tasks
## Create `WARP.md`
Create a `WARP.md` file at the root of your documentation repository to provide Oz with project context:
````markdown theme={null}
# WARP.md
This file provides guidance to WARP (warp.dev) when working with code in this repository.
## Project Overview
This is a **Mintlify documentation site**. Content is written in MDX format and configured via `docs.json`.
## Development Commands
```bash
# Install Mintlify CLI (requires Node.js 19+)
npm i -g mint
# Run local dev server (default: http://localhost:3000)
mint dev
# Run on custom port
mint dev --port 3333
# Update CLI to latest version
npm mint update
# Validate links
mint broken-links
```
## Content Structure
All documentation pages use `.mdx` format with YAML frontmatter. Navigation is tab-based, configured in `docs.json` under `navigation.tabs`.
To add a new page:
1. Create the `.mdx` file in the appropriate directory
2. Add the page path to the relevant group in `docs.json`
## Writing Standards
- Second-person voice ("you")
- Prerequisites at start of procedural content
- Match style and formatting of existing pages
- Relative paths for internal links
- Include both basic and advanced use cases
- Language tags on all code blocks
- Alt text on all images
## Deployment
Changes pushed to the default branch auto-deploy via Mintlify's GitHub integration. No manual build step required.
````
Learn more about Agent Skills at [agentskills.io](https://agentskills.io) and about Oz at [Oz Skills Documentation](https://docs.warp.dev/agent-platform/cloud-agents/skills-as-agents).
# Windsurf setup
Source: https://help.wrld.tech/ai-tools/windsurf
Configure Windsurf for your documentation workflow
Configure Windsurf's Cascade AI assistant to help you write and maintain documentation. This guide shows how to set up Windsurf specifically for your Mintlify documentation workflow.
## Prerequisites
* Windsurf editor installed
* Access to your documentation repository
## Workspace rules
Create workspace rules that provide Windsurf with context about your documentation project and standards.
Create `.windsurf/rules.md` in your project root:
````markdown theme={null}
# Mintlify technical writing rule
## Project context
- This is a documentation project on the Mintlify platform
- We use MDX files with YAML frontmatter
- Navigation is configured in `docs.json`
- We follow technical writing best practices
## Writing standards
- Use second person ("you") for instructions
- Write in active voice and present tense
- Start procedures with prerequisites
- Include expected outcomes for major steps
- Use descriptive, keyword-rich headings
- Keep sentences concise but informative
## Required page structure
Every page must start with frontmatter:
```yaml
---
title: "Clear, specific title"
description: "Concise description for SEO and navigation"
---
```
## Mintlify components
### Callouts
- `` for helpful supplementary information
- `` for important cautions and breaking changes
- `` for best practices and expert advice
- `` for neutral contextual information
- `` for success confirmations
### Code examples
- When appropriate, include complete, runnable examples
- Use `` for multiple language examples
- Specify language tags on all code blocks
- Include realistic data, not placeholders
- Use `` and `` for API docs
### Procedures
- Use `` component for sequential instructions
- Include verification steps with `` components when relevant
- Break complex procedures into smaller steps
### Content organization
- Use `` for platform-specific content
- Use `` for progressive disclosure
- Use `` and `` for highlighting content
- Wrap images in `` components with descriptive alt text
## API documentation requirements
- Document all parameters with ``
- Show response structure with ``
- Include both success and error examples
- Use `` for nested object properties
- Always include authentication examples
## Quality standards
- Test all code examples before publishing
- Use relative paths for internal links
- Include alt text for all images
- Ensure proper heading hierarchy (start with h2)
- Check existing patterns for consistency
````
# Design Guidelines
Source: https://help.wrld.tech/design
WRLD Tech brand tokens used across the docs site
These are the brand tokens used by WRLD Tech Co. across `help.wrld.tech`, `wrld.one`, `wrld.tech`, and related properties. The canonical source is the [`WRLDInc/wrld.one`](https://github.com/WRLDInc/wrld.one) repository — update there first if any token changes, then mirror here.
For the full brand guide (logo usage, spacing, voice), see [Brand Guide](/wrld-tech/brand-guide).
## Color palette
| Token | Hex | Usage |
| ------------ | --------- | -------------------------------------------- |
| Primary Blue | `#00adee` | Primary action color (Vivid Cerulean) |
| Purple | `#3d1f78` | Accent / gradient (Explorer of the Galaxies) |
| Gold | `#d48c2f` | Highlight (Opulent) |
| Dark Navy | `#182534` | Dark mode surfaces and text |
| Light | `#fcfcfc` | Light mode surfaces |
The docs site itself currently uses a blue accent defined in `docs.json` (`colors.primary`, `colors.light`, `colors.dark`) that complements the WRLD primary palette above.
## Typography
| Role | Family | Weights |
| ----------- | ------------- | ------------- |
| Display | Montserrat | 700, 800 |
| Body | Ubuntu | 400, 500, 700 |
| Subheadings | Source Sans 3 | 400, 500, 600 |
The docs site body font is set in `docs.json` (`fonts.family`) and matches the WRLD body font.
## Logo usage
WRLD logos live in the `/logo` directory and ship in light and dark SVG variants. Always use the SVG source; do not re-export or recolor logos ad hoc. Logo URLs for the docs site are configured in `docs.json` under `logo.light` and `logo.dark`.
## Design principles
1. **Clarity** — information should be easy to find and understand.
2. **Consistency** — maintain consistent patterns across products, docs, and marketing.
3. **Accessibility** — design for all users; respect reduced-motion and contrast requirements.
4. **Performance** — prioritize fast, responsive experiences; prefer static content and edge delivery.
# Contributing to these docs
Source: https://help.wrld.tech/development
How to preview, edit, and ship changes to help.wrld.tech
This site is built with [Mintlify](https://mintlify.com) and deployed from the [`WRLDInc/docs`](https://github.com/WRLDInc/docs) repository. Content is authored in MDX, and navigation is configured in `docs.json`.
**Prerequisites**:
* Node.js LTS (Node 22 recommended — Mintlify does not support Node 25+). See [Conda for Node.js](/tools/conda-nodejs) if you need to isolate Node versions per project.
* A docs repository with a `docs.json` file
## Preview locally
```bash theme={null}
npm i -g mint
```
From the repo root (where `docs.json` lives):
```bash theme={null}
mint dev
```
Open `http://localhost:3000`. Pages hot-reload as you edit `.mdx` files.
Before opening a PR:
```bash theme={null}
mint broken-links
```
Use `mint dev --port 3333` to change the port, and `mint update` to upgrade the CLI.
## Add a new page
1. Create an `.mdx` file under the relevant section directory (for example `wrld-host/new-feature.mdx`).
2. Add YAML frontmatter:
```mdx theme={null}
---
title: "Page title"
description: "One-line summary shown in nav and search."
---
```
3. Register the page path (without `.mdx`) in the appropriate group inside `docs.json`:
```json theme={null}
{
"group": "Hosting",
"pages": [
"wrld-host/overview",
"wrld-host/new-feature"
]
}
```
4. Reload `mint dev` and confirm the page appears in the navigation.
5. Run `mint broken-links` and open a pull request.
## Repository layout
See the layout table in [`README.md`](https://github.com/WRLDInc/docs/blob/main/README.md). Each top-level directory maps to a tab or group in `docs.json`.
## Content conventions
* **Voice**: first-person plural ("we") for WRLD, second-person ("you") for the reader.
* **Headings**: use `##` for primary sections — the `title` frontmatter already renders `h1`.
* **Links**: prefer site-relative links (`/support/overview`) for internal pages. External links are always absolute URLs.
* **Brand tokens**: do not hard-code colors or fonts in pages. Reference [Design](/design) or [Brand Guide](/wrld-tech/brand-guide) and update those pages if the brand changes upstream.
* **Source of truth**: WRLD service names, URLs, colors, and typography are mirrored from [`WRLDInc/wrld.one`](https://github.com/WRLDInc/wrld.one). Update there first if a brand token changes.
## Deployment
Merges to the default branch auto-deploy via Mintlify's GitHub integration. There is no separate CI build step.
## Troubleshooting
Usually an outdated Node version. Remove the CLI (`npm remove -g mint`), upgrade to Node 19+, then reinstall (`npm i -g mint`).
Confirm the file path in `docs.json` matches the `.mdx` filename (no extension, no leading slash) and that `mint dev` is running from the directory containing `docs.json`.
Delete `~/.mintlify` and re-run `mint dev`.
# WRLD Tech Co.
Source: https://help.wrld.tech/index
The help center and documentation hub for every WRLD division — tech, host, design, services, support, and AI.
WRLD Tech Co. (WRLD Inc.) is a business technology consultancy organized into six focused divisions. This site is the unified documentation surface for all of them. The canonical public directory lives at [wrld.one](https://wrld.one).
## Divisions
Consulting, development, and systems integration.
Hosting, domains, SSL, email, and VoIP.
Brand identity, design tokens, and logo usage.
Onboarding, workspace setup, and internal tools.
Help center, tickets, security, and remote support.
AI platform services and AI coding tools.
## Start here
Find the right entry point in three steps.
Mission, vision, values, and how we operate.
## The wider WRLD directory
Canonical service directory.
Domain registration and management.
Real-time service status.
Experimental projects.
IPFS gateway.
Blog and announcements.
# Infrastructure
Source: https://help.wrld.tech/infrastructure
How WRLD Tech Co. runs its platforms
WRLD Tech Co. (WRLD Inc.) operates the full stack behind our client-facing services — hosting, DNS, mail, VoIP, remote support, and AI tooling. This page is a high-level overview; deeper guides live under each product section.
## Platforms and stack
| Surface | Platform / stack |
| ----------------------------------- | -------------------------------------------------------------------------------------- |
| `help.wrld.tech` (this site) | Mintlify (MDX content) deployed from [`WRLDInc/docs`](https://github.com/WRLDInc/docs) |
| `wrld.one` (service directory) | [Astro](https://astro.build) on [Cloudflare Workers](https://workers.cloudflare.com) |
| `wrld.host` client area & billing | WHMCS (hosting, domains, SSL, invoicing, ticketing) |
| `wrld.tech` / `wrld.ai` / marketing | WRLD.host shared infrastructure with CDN + SSL |
| `status.wrld.host` | Uptime monitoring and incident history |
| `ipfs.wrld.tech` | IPFS gateway for decentralized content |
The canonical service list is maintained in [`WRLDInc/wrld.one`](https://github.com/WRLDInc/wrld.one). Any new WRLD property should be added there first, then surfaced in these docs and in `docs.json` anchors as appropriate.
## Hosting
WRLD.host provides:
* Shared, reseller, and dedicated hosting
* Domain registration and DNS (including delegated access — see [GoDaddy Delegated Access](/onboarding/domains/godaddy-delegated-access))
* SSL issuance and renewal
* Business email and VoIP services
Hosting is reserved for WRLD clients, which keeps neighbors known and traffic quality predictable.
## Security
* TLS on every public endpoint
* DDoS protection at the edge
* 24/7 infrastructure monitoring
* Managed backups and BCDR for supported plans
* Security guidance for clients under [Support → Security](/support/security/overview), including VPN setup ([Windows](/support/security/vpn/windows), [macOS](/support/security/vpn/macos), [iOS](/support/security/vpn/ios), [Android](/support/security/vpn/android), [Linux](/support/security/vpn/linux))
* Secure file exchange via [SecureSend](/tools/securesend)
## Identity and onboarding
We operate both Microsoft 365 and Google Workspace tenants for clients. Start at:
* [Microsoft 365 initial setup](/onboarding/microsoft-365/initial-setup)
* [Google Workspace overview](/onboarding/google-workspace/overview)
## AI tooling
WRLD.ai is the AI arm of the business. Day-to-day client tooling is documented under [AI Tools](/ai-tools/claude-code) (Claude Code, Cursor, Warp, Windsurf). Platform details live under [WRLD.ai Overview](/wrld-ai/overview).
## Status
Real-time service status is published at [status.wrld.host](https://status.wrld.host).
# GoDaddy Delegated Access
Source: https://help.wrld.tech/onboarding/domains/godaddy-delegated-access
Grant WRLD access to manage your GoDaddy domains
## What is Delegated Access?
Delegated Access allows you to invite WRLD (or any web designer/developer) to access your GoDaddy products without sharing your password. Delegates can manage your domains and hosting but **cannot** view or change sensitive account information like payment methods or passwords.
## How to Invite WRLD as a Delegate
Visit your GoDaddy [Delegate Access](https://account.godaddy.com/access) page. You may be prompted to sign in.
In the **People who can access my account** section, click **Invite to Access**.
Enter the **Name** and **Email** for the person you're inviting.
For WRLD, use:
* **Name**: Ridge Lawrence (or WRLD Tech)
* **Email**: `ridge@wrld.tech`
Choose the appropriate access level. For most domain management tasks, **Products, Domains & Purchase** is sufficient.
Not sure? See GoDaddy's [explanation of access levels](https://www.godaddy.com/help/delegate-access-levels-of-permission-12374).
Click **Invite**. GoDaddy will send an email invitation. Once the delegate accepts, you'll be notified.
## Managing Delegates
### Cancel a Pending Invitation
Pending invitations expire after 48-72 hours if not accepted. To cancel early:
1. Go to [Delegate Access](https://account.godaddy.com/access)
2. Find the pending invitation
3. Click **Cancel**
### Change Access Level
Already granted access but need to adjust permissions?
* [Change a delegate's access level](https://www.godaddy.com/help/change-a-delegates-access-level-12377)
### Remove a Delegate
Need to revoke access?
* [Remove a delegate from your account](https://www.godaddy.com/help/remove-a-delegate-user-from-my-account-19326)
## Domain Folder Permissions
For more granular control over which domains a delegate can access:
* [Assign folder permissions for delegates](https://www.godaddy.com/help/assign-folder-permissions-for-delegates-32180)
## Considering a Transfer?
If you'd like to transfer your domain to WRLD.host for easier management and competitive pricing:
We price-match Namecheap! Link the domain in your order and we'll credit back the difference.
## Need Help?
Contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) if you need assistance with the delegation process. If you have a portal login, you can also [submit a ticket](/support/submit-ticket).
# Google Workspace Overview
Source: https://help.wrld.tech/onboarding/google-workspace/overview
Guides for Google Workspace, Cloud Services, Drive, Chrome, and more
## Google Workspace (G Suite)
Guides and walkthroughs related to Google Workspace, Cloud Services, Business, Drive, Chrome, Groups and other Google Services.
## Available Guides
Configure email on desktop and mobile devices
Cloud storage and file synchronization
Video conferencing and meetings
Scheduling and calendar management
## Shared Mailboxes
Shared mailboxes have become an essential tool for businesses and organizations, allowing teams to collaborate, streamline communication, and efficiently manage emails.
### Benefits of Shared Mailboxes
* **Team Collaboration** - Multiple users can access and respond to emails
* **Streamlined Communication** - Central inbox for department inquiries
* **Email Management** - Organize and track customer communications
* **No Additional Licenses** - Shared mailboxes don't require separate licenses
## Google Admin Console
For IT administrators and managers:
* User management and provisioning
* Security settings and policies
* Device management
* Audit and reporting
## Need Help?
For Google Workspace issues, contact support at [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
# Microsoft 365 Initial Sign-In and 2FA Setup
Source: https://help.wrld.tech/onboarding/microsoft-365/initial-setup
Setup guide for Microsoft 365 with Microsoft Authenticator
## Prerequisites
Before you begin, ensure you have:
* Company Email (Log in using a work or school account)
* Temporary Password Provided by Manager/IT
* Microsoft Authenticator App on Mobile
* Access to Private Network Internet
* (If Bring Your Own Device) Must Be Local Administrator
## Logging In to Your Company Email
The first thing that needs to be done to get your device fully set up with your company is to log in to your company email. This will give you access to your granted apps along with the ability to use SSO (Single Sign On) when accessing said apps.
### Steps
1. Go to [office.com](https://office.com) and click Sign In
2. Type your company email in the email field
3. Enter your temporary password
4. You will be prompted to change your password - change it to something memorable but secure
## Setting Up Two-Factor Authentication (2FA)
After your first login, you will be prompted to set up additional security verification.
### Installing Microsoft Authenticator
1. Download **Microsoft Authenticator** from your device's app store
* [iOS App Store](https://apps.apple.com/app/microsoft-authenticator/id983156458)
* [Google Play Store](https://play.google.com/store/apps/details?id=com.azure.authenticator)
2. Open the app and sign in with your company email
### Linking Your Account
1. When prompted on your computer, select "Next" to begin 2FA setup
2. Choose "Microsoft Authenticator app"
3. Open the Authenticator app on your phone
4. Tap the **+** icon and select "Work or school account"
5. Scan the QR code displayed on your computer screen
6. Approve the test notification sent to your phone
Your company needs this additional security to protect your account and company data.
## Accessing Microsoft 365 Apps
Once setup is complete, you can access:
Email, calendar, and contacts
Chat, meetings, and collaboration
Cloud file storage and sync
Team sites and document libraries
## Need Help?
Contact support at [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) or use the [WRLD Help Button](/support/tickets/help-button).
# WRLD.Services
Source: https://help.wrld.tech/onboarding/overview
Onboarding, workspace setup, device enrollment, and internal tools.
WRLD.Services is where new clients and new hires get set up — identity, workspaces, devices, and the internal tools our team uses to deliver work. Everything web-related (domains, hosting, SSL, email, VoIP) lives under [WRLD.host](/wrld-host/overview).
## Identity & workspaces
Initial sign-in and 2FA with Microsoft Authenticator.
Gmail, Drive, Meet, and shared drives.
## Domains & delegation
Grant WRLD controlled access to a registrar account.
Registration, transfer, and DNS management live under WRLD.host.
## Devices & endpoints
BYOD and corporate devices are enrolled into the company tenant, directory, and MDM — so you can work securely from anywhere.
* Company tenant & EntraID enrollment
* Local Active Directory bind
* MDM (Mobile Device Management)
* RMM & patch agents for Windows, macOS, and Linux
## Internal tools
Secure, expiring credential sharing — never send passwords in plaintext.
Isolate Node versions per project using Conda environments.
## Need help?
The [WRLD.Support](/support/overview) team handles onboarding questions end-to-end.
# Quickstart
Source: https://help.wrld.tech/quickstart
Get up and running with WRLD Tech Co. services
WRLD Tech Co. (WRLD Inc.) is a business technology consultancy. This quickstart points you at the right place to start, depending on what you need.
## Pick the right entry point
Kick off onboarding for Microsoft 365, Google Workspace, or domain delegation.
Open a ticket, request remote support, or reach the help desk.
Access the client area, manage hosting, and browse the knowledgebase.
Learn what AI tooling and integrations WRLD offers.
## Three steps to get started
Email [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech). If you already have a portal login, [open a ticket](/support/submit-ticket). Include your company name, the service you are interested in, and any relevant context.
We'll walk you through identity, domain, and tenant setup. Follow the applicable guide under [Onboarding](/onboarding/overview) (Microsoft 365, Google Workspace, domain delegation).
Sign in at the [WRLD.host client area](https://wrld.host/clientarea.php) to manage services, invoices, and tickets. Bookmark [help.wrld.tech](https://help.wrld.tech) for these docs.
## Getting support
[helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) — monitored during business hours (Mon–Fri, 10am–6pm CT) and after-hours for active clients.
Use the [WRLD client portal](/support/submit-ticket) or the in-page help button on supported sites.
+1 (469) 850-3968 — Mon–Fri + after-hours for active clients.
See [Remote Support](/support/remote-support) for our approved remote-assist tools.
## Next steps
Mission, vision, and values.
Brand, logo, and design tokens.
Guides for Claude Code, Cursor, Warp, and Windsurf.
How WRLD's stack is put together.
# Client Portal Login
Source: https://help.wrld.tech/support/client-login
Sign in to manage tickets, review SLA metrics, and access co-managed IT resources
Access your service tickets, review SLA dashboards, and manage co-managed IT resources through the WRLD client portal.
Continue to the secure Syncro end-user portal to sign in with Google, Microsoft, or your email address and password.
The portal opens at `wrld.syncromsp.com` and displays WRLD Tech Co. branding. If you are not already signed in, Syncro redirects you to the end-user login page.
## What you can access
View, update, and track all your open and resolved support requests in one place.
Monitor your service level agreement metrics, response times, and performance history.
Access shared IT management tools and visibility into your infrastructure.
Don't have a portal account yet? Email [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) to get access set up.
# Contact Support
Source: https://help.wrld.tech/support/contact
How to reach WRLD support
## Contact methods
### Email
Send us an email at [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech)
### Support portal
If you already have a portal login, [sign in to submit a ticket](/support/submit-ticket). Otherwise, email [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) to request access.
### Client portal
Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets and view SLA dashboards.
### Help center
Browse our knowledge base at [wrld.help](https://wrld.help)
## Before contacting support
To help us resolve your issue faster, please have the following ready:
* Your account email or client ID
* A clear description of the issue
* Any relevant error messages or screenshots
* Steps to reproduce the problem (if applicable)
## Response times
* **Critical Issues**: 1-4 hours
* **High Priority**: 4-8 hours
* **Standard Requests**: 24-48 hours
# WRLD.Support
Source: https://help.wrld.tech/support/overview
Help center, tickets, remote support, and security guidance.
WRLD.Support is how clients get help — from self-service articles to live remote sessions. Critical issues are covered 24/7 for active managed clients; standard requests are handled during business hours (Mon–Fri, 10am–6pm CT).
## Get help
Open a new support request or check an existing one.
Sign in to manage tickets and view SLA dashboards.
Email, phone, and escalation paths.
Approved tools for live remote assistance.
## Help button
The fastest way to open a ticket with full diagnostics.
Get it installed on Windows, macOS, or Linux.
## Security
How we verify identity and protect your data.
Zero-trust access to protected resources.
Working with Private Relay on Apple devices.
Share credentials safely — never in plaintext.
## VPN setup
WireGuard on Windows 10/11.
WireGuard on macOS.
WireGuard on iPhone and iPad.
WireGuard on Android.
WireGuard on Linux.
## Hours & response
* **Critical issues**: 1–4 hours (24/7 for active clients)
* **High priority**: 4–8 hours
* **Standard requests**: 24–48 hours
# Remote Support Sessions
Source: https://help.wrld.tech/support/remote-support
How WRLD provides secure remote assistance for your devices
## Getting Remote Support
For quick one-off support sessions, we offer secure remote support for troubleshooting and issue resolution.
### Supported Platforms
| Platform | Support Level |
| -------- | ------------------------ |
| Windows | Full support |
| macOS | Full support |
| Android | Full support |
| Linux | Full support |
| iOS | Managed SLA clients only |
## How Remote Support Works
Submit a support request via the [Help Button](/support/tickets/help-button), [WRLD client portal](/support/submit-ticket), or email [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
Our team will send you a secure session link or meeting invite.
Click the link and approve the connection on your device. You'll see exactly what our tech sees.
Our tech will troubleshoot and resolve your issue while you watch.
The session automatically terminates when complete. No residual access remains.
## Remote Guidance via Teams
If you're not at your computer or need guidance on a mobile device:
Download Teams for Work on your mobile device
Our support team can guide you through steps via video call if screen sharing isn't possible.
## WRLD Patch Agent
For managed clients, we may use the WRLD Patch Agent for remote access and system management.
Windows installation guide
Add to your antivirus exclusions
## Getting Local Admin Access
Some installations require administrator privileges. If you need help getting admin access:
1. Click the WRLD Help Button or chat bubble on [wrld.host](https://wrld.host) or [wrld.tech](https://wrld.tech)
2. Request local admin credentials or elevation assistance
3. Be sure to include any line-of-business (LOB) apps that need pre-whitelisting
## Security & Privacy
* All remote sessions are encrypted
* You can see everything our technician does
* Sessions are logged for security purposes
* No persistent access is granted after the session ends
* We will **never** ask for passwords via email or chat
Learn more about our security-first support approach
# Cloudflare Access (Zero Trust)
Source: https://help.wrld.tech/support/security/cloudflare-access
Install the WARP client and sign in to your organization's Cloudflare One tenant with Microsoft Entra ID or Google Workspace
WRLD uses [Cloudflare Zero Trust](https://www.cloudflare.com/zero-trust/) (also known as **Cloudflare One**) to protect internal applications and client environments. This guide walks you through installing the Cloudflare WARP client on your device and authenticating to your organization's tenant via single sign‑on (SSO).
## Prerequisites
* A device running macOS, Windows, iOS, Android, or Linux.
* An active user account in your organization's identity provider:
* **Microsoft Entra ID** (Azure AD) for Microsoft 365 organizations, or
* **Google Workspace** for Google-based organizations.
* Your organization's **team name** (see below).
**Team names**
* WRLD staff: team name is `wrld`. Tenant URL: [`https://wrld.cloudflareaccess.com`](https://wrld.cloudflareaccess.com).
* SLA‑supported clients: use your **company shortname** issued by WRLD. Tenant URL: `https://.cloudflareaccess.com`.
If you aren't sure of your shortname, check your onboarding email or contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
## Step 1 — Install the Cloudflare WARP client
Download and install from Cloudflare:
* [Cloudflare WARP for macOS](https://1.1.1.1/)
Or install via Homebrew:
```bash theme={null}
brew install --cask cloudflare-warp
```
After install, launch **Cloudflare WARP** from `/Applications`. Accept the warning about installing a system extension/network filter.
Download and install from Cloudflare:
* [Cloudflare WARP for Windows](https://1.1.1.1/)
Or install via `winget`:
```powershell theme={null}
winget install --id Cloudflare.Warp -e
```
After install, launch **Cloudflare WARP** from the Start menu.
Install the **Cloudflare One Agent** from the App Store:
* [Cloudflare One Agent on the App Store](https://apps.apple.com/app/cloudflare-one-agent/id6443476898)
Do **not** use the older "1.1.1.1: Faster Internet" app — that's the consumer app and cannot enroll in a Zero Trust team.
Install the **Cloudflare One Agent** from Google Play:
* [Cloudflare One Agent on Google Play](https://play.google.com/store/apps/details?id=com.cloudflare.cloudflareoneagent)
Follow Cloudflare's per‑distro instructions:
* [Linux install guide (Cloudflare docs)](https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/download-warp/#linux)
Example for Ubuntu/Debian:
```bash theme={null}
curl -fsSL https://pkg.cloudflareclient.com/pubkey.gpg | sudo gpg --yes --dearmor --output /usr/share/keyrings/cloudflare-warp-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/cloudflare-warp-archive-keyring.gpg] https://pkg.cloudflareclient.com/ $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/cloudflare-client.list
sudo apt-get update
sudo apt-get install cloudflare-warp
```
## Step 2 — Enroll in your organization's team
* **Desktop** (macOS / Windows / Linux): click the WARP menu-bar / system-tray icon → the gear icon → **Preferences** → **Account**.
* **Mobile** (iOS / Android): open **Cloudflare One Agent** → **Settings** (gear) → **Account**.
Select **Login to Cloudflare Zero Trust** (on mobile this may be **Login with SSO**).
When prompted for a team name, enter:
* `wrld` — if you're WRLD staff.
* `` — your client shortname issued by WRLD (e.g. `acme`).
You enter **only the team name**, not the full URL. Cloudflare will route you to `https://.cloudflareaccess.com` automatically.
A browser window opens to `https://.cloudflareaccess.com`. You'll see a list of available identity providers. Proceed to the appropriate section below.
## Step 3 — Authenticate with your identity provider
Choose this if your organization uses Microsoft 365, Azure AD, or Entra ID for user accounts.
On the Cloudflare Access login page, click **Sign in with Microsoft** (or the button labeled with your organization's Entra ID tenant name).
Enter your work email (e.g. `you@yourcompany.com`) and password, then complete MFA (Microsoft Authenticator push, code, or FIDO2 key — whichever your tenant enforces).
If this is your first login, you may be asked to accept permissions for the Cloudflare Access app. Your org may have pre‑consented, in which case this step is skipped.
After successful login, the browser displays a "You may close this window" / "Success" page. Return to the WARP client — it should now show **Connected** with your user identity.
Choose this if your organization uses Google Workspace (Gmail / Google-managed accounts) for user accounts.
On the Cloudflare Access login page, click **Sign in with Google** (or the button labeled with your organization's Workspace domain).
Choose your work account and complete 2‑Step Verification (prompt, code, or security key).
Make sure you select your **work** Google account, not a personal `@gmail.com` account. Personal accounts will be rejected by the access policy.
If your Workspace admin hasn't pre‑authorized the Cloudflare Access app, you'll be prompted to allow access. Accept to proceed.
After a "Success" page, return to the WARP client. Its status should switch to **Connected** with your user identity displayed.
## Step 4 — Verify your connection
The WARP client should show:
* **Status**: Connected
* **Mode**: Zero Trust (or similar, depending on client version)
* **Account**: your work email address
Open [`https://.cloudflareaccess.com/cdn-cgi/trace`](https://wrld.cloudflareaccess.com/cdn-cgi/trace) in a browser. You should see `warp=on` and `gateway=on` in the output.
Navigate to an internal application covered by your org's Access policy. You should be allowed in without seeing the Access login page again (SSO is now cached in WARP).
## Daily use
* The WARP client re‑authenticates automatically based on your org's session duration. You may be prompted to sign in again every 24 hours, 7 days, or 30 days depending on policy.
* To temporarily disconnect, toggle WARP off from the menu‑bar/tray icon. **Protected apps will stop working** until you reconnect.
* To switch between the consumer 1.1.1.1 VPN and your Zero Trust team, use **Preferences → Account → Logout from Zero Trust**, then log in fresh.
## Troubleshooting
Double-check you entered the correct team name (no URL, no `https://`, no `.cloudflareaccess.com` suffix). For WRLD staff it's `wrld`. For SLA clients, your shortname was issued by WRLD — check your onboarding email or contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
Your tenant may only have one IdP configured, in which case the login page might go directly to that provider without showing a picker. If you expect to see both Microsoft and Google options and don't, ask WRLD support to confirm which IdPs are enabled for your tenant.
You authenticated successfully, but the Access policy denied you. Common causes:
* Your user account isn't in the required group (e.g. `WRLD-Staff`, or a client-specific group).
* Your device doesn't meet posture requirements (OS version, disk encryption, etc.).
* You're connecting from a geography or IP the policy excludes.
Capture the **Ray ID** shown on the denial page and send it to [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
* Fully quit and reopen the WARP client.
* On macOS: check **System Settings → Network** for a "Cloudflare WARP" interface; toggle it off/on.
* On Windows: restart the **Cloudflare WARP** service from `services.msc`.
* Ensure your device clock is accurate — large clock skew breaks TLS.
* If you're on a restrictive network (e.g. hotel Wi-Fi), it may block MASQUE/WireGuard traffic. Try another network to isolate.
WARP overrides DNS. If a specific internal hostname doesn't resolve:
* Ensure your org's Gateway policy includes the required domains.
* On macOS, run `scutil --dns` to confirm WARP's resolver is active.
* Contact WRLD support so we can review the Gateway DNS policy.
Running two VPNs at once often breaks routing. Disconnect your site‑to‑site VPN (see [VPN Setup](/support/security/vpn/macos)) before connecting WARP, or ask WRLD to carve out split‑tunnel exceptions for the overlapping subnets.
On iOS and Android, the standalone "1.1.1.1" app is the consumer WARP client and cannot enroll in a team. Install **Cloudflare One Agent** instead (links in Step 1).
## Need help?
Email [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) with:
* Your team name / shortname.
* The platform and WARP client version (visible under **Preferences → About**).
* Any error message shown, plus the Cloudflare **Ray ID** if one was displayed.
## References
* [Cloudflare Zero Trust docs](https://developers.cloudflare.com/cloudflare-one/)
* [WARP client download](https://1.1.1.1/)
* [Connect devices with WARP](https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/)
# Disable Limit IP Address Tracking (iOS)
Source: https://help.wrld.tech/support/security/ios-private-relay
Turn off Private Relay and IP tracking limits for managed networks
## What is Limit IP Address Tracking?
iOS includes a feature called **Limit IP Address Tracking** (part of iCloud Private Relay) that hides your real IP address from websites and network services. While this enhances privacy on public networks, it can cause issues on managed corporate or home networks.
## When to Disable It
You may need to disable this feature if:
* Your VPN connection won't establish
* You can't access internal company resources
* Network-based authentication isn't working
* Your IT team requests it for troubleshooting
## How to Turn Off Limit IP Address Tracking
Tap the **Settings** app on your home screen.
Tap **Wi-Fi** to see the list of available networks.
Tap the **ⓘ** (information icon) next to the network you're currently connected to.
Scroll down and find **Limit IP Address Tracking**.
Toggle it **off** to disable this feature for this network.
This setting is per-network. You'll need to disable it separately for each Wi-Fi network where you need full connectivity.
## Why It's Safe on Managed Networks
Disabling this feature on a **secure, managed network** (like your office) is generally safe because:
1. **Secure Environment** - Managed networks have firewalls, intrusion detection, and regular monitoring
2. **Trustworthy Network** - IT staff maintain security and minimize vulnerabilities
3. **Controlled Access** - Not just anyone can join the network, reducing risk
## When to Keep It Enabled
Keep **Limit IP Address Tracking** enabled on:
* Public Wi-Fi (cafes, airports, hotels)
* Untrusted networks
* Networks where you don't need to access corporate resources
## Possible Issues When Disabled
* Your real IP address will be visible to websites and services
* Some geo-restricted content may behave differently
* Minor performance differences on some networks
## Conclusion
Turning off Limit IP Address Tracking is safe on secure, managed networks and may improve performance or fix connectivity issues. Use discretion based on the network you're connected to.
## Related Guides
Configure WireGuard VPN on iPhone/iPad
Similar settings apply to macOS Private Relay
# Security-First Support
Source: https://help.wrld.tech/support/security/overview
Security and privacy-first support practices
## Security-and-Privacy-First Support
At WRLD, we prioritize your security and privacy in every interaction.
## Secure Credential Sharing
Never send passwords in plaintext! Use our secure sharing tool.
## Verifying Our Support Team
Before sharing any sensitive information, verify you're communicating with legitimate WRLD support:
* Official emails come from `@wrld.tech` domains
* Support tickets are always handled through official channels
* We will **never** ask for full passwords via email or chat
* When in doubt, call us directly to verify
## VPN Setup (WireGuard)
Setup instructions for VPN access to corporate or private networks on various devices:
* Windows
* macOS
* iOS
* Android
* Linux
VPN access may be required for accessing internal company resources securely.
## Remote Support Sessions
For quick one-off support sessions, we offer secure remote support for:
* **Windows** - Full support
* **Mac** - Full support
* **Android** - Full support
* **Linux** - Full support
* **iOS** - Managed SLA clients only
### How Remote Support Works
1. Request a support session via ticket or Help Button
2. Receive a secure session link
3. Approve the connection on your device
4. Our tech assists with your issue
5. Session automatically terminates when complete
## Best Practices
For sharing passwords and sensitive data
Always verify support personnel
Connect via VPN when required
Alert us to any suspicious requests
# VPN Setup - Android
Source: https://help.wrld.tech/support/security/vpn/android
Configure WireGuard VPN on Android devices
## Prerequisites
* Android 5.0 or later
* WireGuard configuration file or QR code (provided by WRLD)
## Installation
Download WireGuard from the [Google Play Store](https://play.google.com/store/apps/details?id=com.wireguard.android).
**Option A: Scan QR Code**
1. Open WireGuard
2. Tap the **+** button (blue floating button)
3. Select **Scan from QR code**
4. Allow camera access and scan the QR code
5. Name the tunnel and tap the checkmark
**Option B: Import File**
1. Tap the **+** button
2. Select **Import from file or archive**
3. Navigate to your `.conf` file and select it
Tap the toggle switch next to your tunnel name. Android will ask permission to set up a VPN connection—tap **OK**.
## Quick Settings Tile
Add WireGuard to your Quick Settings:
1. Swipe down twice to open Quick Settings
2. Tap the pencil/edit icon
3. Find "WireGuard" and drag it to your active tiles
4. Now you can toggle VPN with one tap
## Troubleshooting
* Disable battery optimization for WireGuard
* Go to **Settings > Apps > WireGuard > Battery > Unrestricted**
* Check if another VPN app is interfering
* Verify the configuration file is correct
* Try restarting your device
* Ensure the `.conf` file is accessible
* Check file permissions in your file manager
## Need Help?
Contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
# VPN Setup - iOS
Source: https://help.wrld.tech/support/security/vpn/ios
Configure WireGuard VPN on iPhone and iPad
## Prerequisites
* iOS 15 or later
* WireGuard configuration file or QR code (provided by WRLD)
## Installation
Download WireGuard from the [App Store](https://apps.apple.com/us/app/wireguard/id1441195209).
**Option A: Scan QR Code**
1. Open WireGuard
2. Tap the **+** button
3. Select **Create from QR code**
4. Scan the QR code provided by WRLD
5. Name the tunnel and tap **Save**
**Option B: Import File**
1. Open the `.conf` file sent to you (via email, AirDrop, etc.)
2. Tap **Share** and select **WireGuard**
3. The configuration will be imported automatically
iOS will ask permission to add a VPN configuration. Tap **Allow** and authenticate with Face ID, Touch ID, or passcode.
Toggle the switch next to your tunnel name to connect.
## Quick Access
Add the VPN toggle to Control Center:
1. Go to **Settings > Control Center**
2. Add **VPN** to included controls
3. Swipe down from the top-right corner to toggle
## Important: Disable Private Relay
If you're using iCloud Private Relay, it may interfere with VPN connectivity. See our guide on [disabling Limit IP Address Tracking](/support/security/ios-private-relay).
## Troubleshooting
* Ensure you have a stable internet connection
* Disable Private Relay/Limit IP Address Tracking
* Try connecting on a different network
* Ensure good lighting and a clear view of the code
* Request a configuration file instead
## Need Help?
Contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
# VPN Setup - Linux
Source: https://help.wrld.tech/support/security/vpn/linux
Configure WireGuard VPN on Linux
## Prerequisites
* Linux distribution with kernel 5.6+ (or wireguard-dkms for older kernels)
* WireGuard configuration file (provided by WRLD)
* Root/sudo access
## Installation
```bash theme={null}
sudo apt update
sudo apt install wireguard
```
```bash theme={null}
sudo dnf install wireguard-tools
```
```bash theme={null}
sudo pacman -S wireguard-tools
```
```bash theme={null}
sudo yum install epel-release elrepo-release
sudo yum install kmod-wireguard wireguard-tools
```
## Configuration
Copy your `.conf` file to the WireGuard directory:
```bash theme={null}
sudo cp /path/to/wrld.conf /etc/wireguard/wrld.conf
sudo chmod 600 /etc/wireguard/wrld.conf
```
```bash theme={null}
sudo wg-quick up wrld
```
You should see output indicating the interface is configured.
```bash theme={null}
sudo wg show
```
This displays the active tunnel, peer information, and transfer statistics.
## Disconnect
```bash theme={null}
sudo wg-quick down wrld
```
## Auto-Start on Boot
To start the VPN automatically:
```bash theme={null}
sudo systemctl enable wg-quick@wrld
sudo systemctl start wg-quick@wrld
```
## Troubleshooting
Ensure you're running the command with `sudo` and that the WireGuard kernel module is loaded:
```bash theme={null}
sudo modprobe wireguard
```
Install the resolvconf package:
```bash theme={null}
# Ubuntu/Debian
sudo apt install resolvconf
# Or use systemd-resolved
sudo apt install systemd-resolved
```
* Check firewall rules (UDP port 51820 must be allowed outbound)
* Verify your configuration file is correct
* Ensure your IP is whitelisted on the server
## Need Help?
Contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
# VPN Setup - macOS
Source: https://help.wrld.tech/support/security/vpn/macos
Configure WireGuard VPN on macOS
## Prerequisites
* macOS 10.14 or later
* WireGuard configuration file (provided by WRLD)
## Installation
Download WireGuard from the [Mac App Store](https://apps.apple.com/us/app/wireguard/id1451685025).
Alternatively, install via Homebrew:
```bash theme={null}
brew install wireguard-tools
```
1. Open WireGuard from Applications
2. Click **Import tunnel(s) from file** (or drag the `.conf` file onto the app)
3. Approve any system permission prompts
4. The tunnel will appear in your list
1. Select your tunnel from the list
2. Click **Activate**
3. You may need to enter your macOS password
4. The status will show "Active"
## Menu Bar Access
Once configured, you can quickly toggle the VPN from the menu bar:
* Click the WireGuard icon in the menu bar
* Select your tunnel to activate/deactivate
## Troubleshooting
* Go to **System Settings > Privacy & Security > VPN**
* Ensure WireGuard is allowed to add VPN configurations
* Verify the `.conf` file is valid
* Check that you received the correct file from WRLD
* Check if Private Relay is disabled (see [iOS Private Relay guide](/support/security/ios-private-relay))
* Verify your IP is whitelisted
## Need Help?
Contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) or use the [Help Button](/support/tickets/help-button).
# VPN Setup - Windows
Source: https://help.wrld.tech/support/security/vpn/windows
Configure WireGuard VPN on Windows
## Prerequisites
* Windows 10 or later
* WireGuard configuration file (provided by WRLD)
* Administrator access
## Installation
Download the official WireGuard client from [wireguard.com/install](https://www.wireguard.com/install/).
Click **Download Windows Installer** and run the installer.
1. Open WireGuard from the Start menu
2. Click **Import tunnel(s) from file**
3. Select the `.conf` file provided by WRLD
4. The tunnel will appear in your list
1. Select your tunnel from the list
2. Click **Activate**
3. The status will change to "Active" with a green indicator
## Verify Connection
Once connected, you should see:
* **Status**: Active
* **Transfer**: Data sent/received values increasing
* **Latest handshake**: Recent timestamp
## Troubleshooting
* Check your internet connection
* Verify the configuration file is correct
* Ensure no other VPN is active
* Check if your IP is whitelisted on the target network
* Verify DNS settings in the configuration
* Contact WRLD support for assistance
* Try a different network (avoid restrictive corporate firewalls)
* Check if your ISP blocks UDP traffic on port 51820
## Need Help?
Contact [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) or use the [Help Button](/support/tickets/help-button).
# Submit a Ticket
Source: https://help.wrld.tech/support/submit-ticket
Sign in to the WRLD client portal to create or manage a support ticket
Create a new support request and review existing tickets in the secure WRLD client portal.
Continue to the Syncro end-user portal. Sign in with Google, Microsoft, or your email address and password, then create or manage your service tickets.
Ticket submission requires a portal login. The portal opens at `wrld.syncromsp.com` and displays WRLD Tech Co. branding.
Need help urgently? Call us directly at [+1 (469) 850-3968](tel:+14698503968) or email [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech).
# WRLD Help Button
Source: https://help.wrld.tech/support/tickets/help-button
1-Click-and-Done Problem Resolution - Best Method for Getting Support
## How To Use The WRLD Help Desk Button
**Skip the screenshots and the facetime calls.** The BUTTON made by our partner Tier2 is here to help - we'll spare you the technical details, diagnostics and screengrabs it automatically provides to help us better help you and get straight to it.
Follow our quick install guide to get the Help Button on your device.
## Where Can I Find It?
Look for our logo with **HELP** in one of these locations:
* **Your Taskbar!** Look for our logo with 'HELP' and simply click it
* **Your Desktop Icon** (Mixed in with other icons like the Trash Bin)
* **By Pressing F1** (if configured)
* **By right-clicking** your system tray
## How to Submit a Diagnostic Helpdesk Ticket
**First time running?** You'll be prompted to enter your contact info (email/phone). This only happens once per user.
### Watch the Walkthrough
### Steps
1. **Click the WRLD Help Button** in your taskbar or desktop
2. **Describe your issue** in the ticket form to the best of your ability
3. **Review AI suggestions** - You may be shown solutions to try first. Click "None of these, Continue" if they don't help.
4. **Confirm consent** - Acknowledge that you're not sending protected/confidential information
5. **Submit and receive your ticket number**
## Why Use the Help Button?
Captures your last 10 clicks and system health automatically
No need to take and attach screenshots manually
Get help quicker with all the info we need upfront
Receive a ticket number to track your request
## Not on a Company Device?
If you're on your mobile or don't see the Help Button, you can still submit tickets:
Sign in to the secure client portal to submit tickets
Right-click the portal icon in your system tray
See more at [help.wrld.tech](https://help.wrld.tech)
# Install the WRLD Help Button
Source: https://help.wrld.tech/support/tickets/help-button-install
Self-install walkthrough for the WRLD Help Desk Button
## Download & Install
The WRLD Help Button makes submitting support tickets fast and easy. Follow these steps to install it on your Windows device.
Download the MSI installer file:
WRLD Help Button - Self Install-1.17.40.msi
The file will download to your default save folder.
Double-click the downloaded `.msi` file to run it.
You may need to right-click and select "Run as Administrator" or approve security alerts.
When prompted, select which function key to assign to the Help Button.
**We recommend selecting F1** for quick access.
The installer will ask you to restart your computer. Select "Yes" to complete the installation.
## After Installation
Once installed, you can access the Help Button from:
* **Taskbar** - Look for the WRLD logo with "HELP"
* **Desktop** - Icon alongside other desktop icons
* **F1 Key** - Press F1 (if configured during install)
* **System Tray** - Right-click the tray icon
See our guide on submitting tickets with the Help Button
## Need Help?
If you encounter issues during installation, contact us at [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) or call **469.299.9598**.
# Conda for Node.js
Source: https://help.wrld.tech/tools/conda-nodejs
Isolate Node.js versions per project with Miniconda on macOS
This guide sets up [Miniconda](https://www.anaconda.com/docs/getting-started/miniconda/main) as a per‑project Node.js version manager on macOS. It's the recommended approach for WRLD team machines that already use conda for Python work, or where tools (like [Mintlify](/development)) require a specific Node LTS that conflicts with the system Node.
**When to use this vs. `nvm` / `fnm`**
* Use conda if you already rely on it for Python, or if you want one tool to manage both Node and Python environments.
* Use [`fnm`](https://github.com/Schniz/fnm) or [`nvm`](https://github.com/nvm-sh/nvm) if this machine is mostly JavaScript/Node — they're lighter and honor `.nvmrc` / `.node-version` files automatically.
## Prerequisites
* macOS (Apple Silicon or Intel)
* Admin access to your user account (no `sudo` required for the steps below)
* `zsh` (the default shell on modern macOS)
## Install Miniconda
Apple Silicon (M1/M2/M3/M4):
```bash theme={null}
curl -O https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-arm64.sh
```
Intel Macs:
```bash theme={null}
curl -O https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-x86_64.sh
```
```bash theme={null}
bash Miniconda3-latest-MacOSX-arm64.sh
```
Accept the license, accept the default install location (`~/miniconda3`), and answer **yes** when asked whether to update your shell profile.
Close and reopen your terminal, or run:
```bash theme={null}
source ~/.zshrc
```
Verify:
```bash theme={null}
conda --version
```
By default, conda activates its `base` environment in every new terminal. To disable that:
```bash theme={null}
conda config --set auto_activate_base false
```
Newer conda releases require explicit ToS acceptance for the default Anaconda channels before you can install packages:
```bash theme={null}
conda tos accept --override-channels --channel https://repo.anaconda.com/pkgs/main
conda tos accept --override-channels --channel https://repo.anaconda.com/pkgs/r
```
```bash theme={null}
rm ~/Miniconda3-latest-MacOSX-arm64.sh
```
## Create a Node environment
Create one environment per project and pin the Node major version. Use the `conda-forge` channel — it ships more current Node builds than `defaults`.
```bash theme={null}
conda create -n -c conda-forge nodejs= -y
```
Example — a dedicated env for this docs site (Mintlify requires Node LTS):
```bash theme={null}
conda create -n docs-mintlify -c conda-forge nodejs=22 -y
```
Pinning `nodejs=22` prevents conda from silently upgrading you to a non‑LTS release on the next `conda update`.
## Daily workflow
```bash theme={null}
# Activate the env for this project
conda activate docs-mintlify
# Verify the right Node is active
node -v # should match the version you pinned
which node # should point inside ~/miniconda3/envs//bin/
# Install project dependencies as usual
npm install
# or install a CLI globally *into the env*
npm i -g mint
# When you're done
conda deactivate
```
Global npm installs (`npm i -g ...`) while an env is active install into that env only — they won't pollute your system Node or other envs. This is the whole point of using conda for Node.
## Managing environments
```bash theme={null}
# List all envs
conda env list
# Update Node inside an active env
conda update -c conda-forge nodejs
# Remove an env entirely
conda env remove -n
# Export an env so teammates can reproduce it
conda env export -n > environment.yml
# Recreate from an exported file
conda env create -f environment.yml
```
## Example: running `mint dev` for this docs site
```bash theme={null}
conda create -n docs-mintlify -c conda-forge nodejs=22 -y
conda activate docs-mintlify
npm i -g mint
```
```bash theme={null}
cd ~/repos/docs
conda activate docs-mintlify
mint dev
```
The preview runs at [http://localhost:3000](http://localhost:3000).
## Troubleshooting
Your shell hasn't been initialized for conda. Run once:
```bash theme={null}
/Users//miniconda3/bin/conda init zsh
source ~/.zshrc
```
If that still fails, source conda's hook directly in the current shell:
```bash theme={null}
source ~/miniconda3/etc/profile.d/conda.sh
```
A globally installed Node is shadowing the env. Confirm with:
```bash theme={null}
which -a node
```
The first result should be inside `~/miniconda3/envs//bin/`. If it isn't, check your `~/.zshrc` / `~/.zprofile` for a stray `PATH` export (e.g. from a previous Homebrew `node` install) that's prepended *after* conda's init block. Move conda's init below those lines, or uninstall the shadowing Node:
```bash theme={null}
brew uninstall node
```
You haven't accepted the Anaconda channel Terms of Service yet. Run:
```bash theme={null}
conda tos accept --override-channels --channel https://repo.anaconda.com/pkgs/main
conda tos accept --override-channels --channel https://repo.anaconda.com/pkgs/r
```
The env doesn't exist yet — `conda activate` can only activate envs that were already created with `conda create`. List what you have:
```bash theme={null}
conda env list
```
Then create the one you need (see [Create a Node environment](#create-a-node-environment)).
You're running a non‑LTS Node. Activate an env pinned to Node 22 (or any current LTS) and reinstall the CLI *inside* that env:
```bash theme={null}
conda activate docs-mintlify
npm i -g mint
mint dev
```
## Related
* [Local Mintlify development](/development)
* [Miniconda documentation](https://www.anaconda.com/docs/getting-started/miniconda/main)
* [conda-forge Node.js package](https://anaconda.org/conda-forge/nodejs)
# SecureSend - Secure Password Sharing
Source: https://help.wrld.tech/tools/securesend
Send passwords and sensitive information securely - Never send plaintext!
## SecureSend.WRLD.Tech
**Never send passwords or sensitive information in plaintext!** Use [SecureSend.WRLD.Tech](https://securesend.wrld.tech) to securely share credentials with our support team or colleagues.
## How It Works
All passwords are encrypted prior to storage and are available to only those with the secret link. Once expired, encrypted passwords are unequivocally deleted from the database.
## Step by Step: How to Send Secure Notes and Passwords
1. Go to [securesend.wrld.tech](https://securesend.wrld.tech)
2. Type the secure info or password you want to share
3. Adjust settings per preference (e.g., how many views before self-destructing - defaults at 7)
4. Click **PUSH IT!**
5. Copy the generated URL or QR Code
6. Paste the URL or QR Image in the email/ticket/message
7. Done!
## Security Features
All data is encrypted before being stored
Links expire after set time or number of views
Optional step to avoid chat systems eating up views
Allow recipients to delete after retrieval
## Configuration Options
* **Expire after X days** - Set how long the link remains active
* **Expire after X views** - Set maximum number of retrievals
* **1-click retrieval step** - Helps avoid URL scanners from using up views
* **Allow immediate deletion** - Let users delete the push once retrieved
* **Passphrase lockdown** - Add additional password protection
Only enter a password into the box. Other identifying information can compromise security.
## Try It Now
Create your first secure link
# WRLD.AI
Source: https://help.wrld.tech/wrld-ai/overview
AI platform services and the coding tools WRLD recommends day-to-day.
WRLD.AI is the AI arm of WRLD Tech Co. It covers both the AI platform services we build for clients and the day-to-day coding tools we support internally and in the field.
## Platform services
Custom chatbots and virtual assistants tied to your business data.
Intelligent automation across CRMs, ticketing, and ops.
AI-powered analysis of business and operational data.
Connect AI capability into existing systems and stacks.
## AI coding tools
Anthropic's coding agent for the terminal.
AI-native IDE built on VS Code.
Modern terminal with AI built in.
Agentic IDE with collaborative AI flows.
## Get started
Reach out at [ai@wrld.tech](mailto:ai@wrld.tech) to explore how AI fits into your business.
# WRLD.design
Source: https://help.wrld.tech/wrld-design/overview
Brand identity, design tokens, and logo usage for the WRLD ecosystem.
WRLD.design owns the look and feel of everything that carries the WRLD name — from the docs site to marketing surfaces and client deliverables. The canonical tokens live in [`WRLDInc/wrld.one`](https://github.com/WRLDInc/wrld.one); this section is the mirrored, human-readable reference.
## Design system
Colors, typography, voice, and principles.
Condensed token tables used across the docs.
SVG sources, clearspace, and do-not rules.
## Services
Logo, color system, and typographic hierarchy for new WRLD properties and client brands.
Product and marketing interface design, aligned to WRLD brand primitives.
Landing pages, collateral, and campaign assets delivered on WRLD infrastructure.
Reviews of partner or vendor work to ensure brand consistency.
## Principles
1. **Clarity** — information should be easy to find and understand.
2. **Consistency** — the same patterns across products, docs, and marketing.
3. **Accessibility** — respect contrast, motion, and keyboard navigation.
4. **Performance** — prioritize fast, edge-delivered experiences.
## Related
Engineering side of the house.
Start a design engagement.
# Getting Started with WRLD.host
Source: https://help.wrld.tech/wrld-host/getting-started
Set up your hosting account and get online
## Step 1: Create an Account
Visit [wrld.host](https://wrld.host) and sign up for an account.
## Step 2: Choose a Plan
Select the hosting plan that best fits your needs:
* **Shared Hosting** - Perfect for small websites and blogs
* **VPS Hosting** - For growing businesses needing more resources
* **Dedicated Servers** - Maximum performance and control
## Step 3: Configure Your Domain
Point your domain to our nameservers or use our domain registration service.
## Step 4: Deploy Your Site
Upload your files via FTP, use our one-click installers, or connect your Git repository.
## Need Help?
Contact our support team at [helpdesk@wrld.tech](mailto:helpdesk@wrld.tech) or visit [wrld.help](https://wrld.help).
# WRLD.host Knowledge Base
Source: https://help.wrld.tech/wrld-host/knowledgebase
Product documentation and guides for WRLD.host services
## Product Knowledge Base
For detailed product documentation, tutorials, and how-to guides for WRLD.host services, visit our main knowledge base:
Complete documentation for all hosting products and services
***
## Hosting
Private, invite-only hosting for trusted entities
Fast, reliable, and secure WordPress hosting
Powerful cloud VPS with dedicated resources
WHM access for managing multiple sites
## Servers
Root access, SSD storage, blazing-fast networking
Industry-leading hardware at affordable prices
High performance with minimal ping
## Domains
Register a new domain
Transfer your domain to WRLD
Manage your domains
## Security & Tools
Secure your site with SSL/TLS
Daily automated backups
Find problems before your visitors do
Malware scanning and protection
## DIY Site Building
Building a website has never been easier
Simple tools for your big ideas
## Email & Productivity
Powerful email and productivity apps for any-size business
## SEO & Marketing
Improve traffic and grow your business
Server-grade SEO features for next-level edge
***
## Need Help?
Open a support ticket
Chat with us on wrld.host
# WRLD.host
Source: https://help.wrld.tech/wrld-host/overview
Hosting, domains, SSL, business email, and VoIP — the full web stack.
WRLD.host is where every web-related service lives: hosting, domain registration, SSL, business email, VoIP, and the client area. Hosting is reserved for WRLD clients, which keeps neighbors known and traffic quality predictable.
## Hosting
Fast, managed shared hosting for small sites and apps.
Virtual private and cloud servers with full control.
Dedicated hardware and reseller plans for agencies.
## Domains
Search for and register new domains.
Bring an existing domain to WRLD.
DNS, nameservers, and GoDaddy delegated access.
## SSL & website security
Issuance, renewal, and managed TLS for every domain.
Automated backups and uptime monitoring.
## Email & VoIP
Professional mailboxes tied to your domain.
Business phone numbers and hosted voice.
## Client area
Set up your first hosting account.
Browse the full WRLD.host knowledge base.
Manage services, invoices, and tickets.
Live uptime and incident history.
# Brand Guide
Source: https://help.wrld.tech/wrld-tech/brand-guide
WRLD Tech Co. brand identity, colors, typography, and logo usage
The canonical WRLD brand guide lives in the [`WRLDInc/wrld.one`](https://github.com/WRLDInc/wrld.one) repository and is mirrored here for reference by partners, vendors, and clients. Any change to these tokens should be made in `wrld.one` first, then reflected here and in [`docs.json`](https://github.com/WRLDInc/docs/blob/main/docs.json).
## Colors
| Name | Hex | Role |
| ----------------------------- | --------- | ------------------------------------ |
| Vivid Cerulean (Primary Blue) | `#00adee` | Primary brand color, primary actions |
| Explorer of the Galaxies | `#3d1f78` | Accent / gradients |
| Opulent (Gold) | `#d48c2f` | Highlight / premium emphasis |
| Dark Navy | `#182534` | Dark mode surfaces and text |
| Light | `#fcfcfc` | Light mode surfaces |
Gradients combining Vivid Cerulean and Explorer of the Galaxies are reserved for hero moments and primary marketing surfaces.
## Typography
| Role | Family | Weights | Notes |
| ----------- | ------------- | ------------- | --------------------------------------- |
| Display | Montserrat | 700, 800 | Headlines, hero type |
| Body | Ubuntu | 400, 500, 700 | Default body; used across the docs site |
| Subheadings | Source Sans 3 | 400, 500, 600 | Eyebrows, captions, UI labels |
The docs site body font is pinned to Ubuntu via `docs.json` (`fonts.family`).
## Logo
* Use the SVG source files in the repo's `/logo` directory — do not re-export from screenshots.
* Keep clearspace around the logo equal to the height of the "W" glyph on all sides.
* Use the light-mode logo on light backgrounds (`#fcfcfc` and near-white) and the inverse logo on dark backgrounds (`#182534` and near-black).
* Do not stretch, recolor, add drop shadows, or place the logo on low-contrast photography.
## Voice and tone
* First-person plural ("we") when speaking for WRLD, second-person ("you") to the reader.
* Direct and confident, never flippant. Clients entrust us with business-critical systems — write like it.
* Prefer short sentences and concrete nouns. Avoid marketing filler and unnecessary qualifiers.
## Design principles
1. **Clarity** — information should be easy to find and understand.
2. **Consistency** — maintain consistent patterns across products, docs, and marketing.
3. **Accessibility** — respect contrast, motion, and keyboard-navigation requirements.
4. **Performance** — prioritize fast, edge-delivered experiences.
## Related
* [Design Guidelines](/design) — the condensed token table used by contributors to this docs site.
* [WRLD.one on GitHub](https://github.com/WRLDInc/wrld.one) — canonical source for brand tokens.
# WRLD.tech
Source: https://help.wrld.tech/wrld-tech/overview
Technology consulting, development, and systems integration.
WRLD.tech is the consulting and engineering arm of WRLD Tech Co. We design, build, and integrate the systems that run our clients' businesses — then tie them back to the rest of the WRLD stack (hosting, AI, support) so you don't have to stitch vendors together.
## What we do
Custom websites, web apps, and API integrations.
Design, migration, and optimization across major cloud providers.
On-site networking, firewalls, VoIP, and secure remote access.
Connect CRMs, accounting, marketing, and bespoke tooling.
Embed AI capabilities into existing business workflows.
Hardening, monitoring, and policy alignment for SMB clients.
## How we engage
We scope the work, identify constraints, and align on outcomes.
Architecture and approach are documented before build starts.
Delivered on WRLD infrastructure where it makes sense; trusted partners where it does not.
Ongoing support via [WRLD.Support](/support/overview) with optional managed plans.
## Related
How the WRLD stack is put together.
Start a project or ask a question.
#### Videos
Use the HTML video element for self-hosted video content:
Embed YouTube videos using iframe elements:
#### Tooltips
Example of tooltip usage: