Setting up Inwire for Your Organization

This guide covers how Organization and Team Administrators configure Inwire for their teams. You'll learn how to set up integrations, configure environments, and manage access controls.

---

Prerequisites

Before setting up Inwire, ensure:

• You have Org Admin or Team Admin privileges
• Your Inwire instance is deployed and accessible
• You have credentials for any external services you want to integrate

---

Configuring Integrations

Integrations connect Inwire to your existing infrastructure. They enable features like:

• Storing datasets and models in cloud storage
• Pulling code from version control
• Deploying models to cloud providers
• Authenticating with external services

Accessing Integrations

1. Navigate to Access Control in the sidebar
2. Select your Team or Organization
3. Click the Integrations tab

Cloud Storage Integrations

Cloud storage is essential for storing datasets, model artifacts, and generated data.

Amazon S3

Field	Description	Example
Name	Friendly identifier	"Production S3"
Bucket	S3 bucket name	"acme-ml-data"
Region	AWS region	"us-east-1"
Access Key ID	AWS access key	(from IAM)
Secret Access Key	AWS secret key	(from IAM)

> Security Note: Use IAM roles when running on AWS infrastructure instead of access keys.

Google Cloud Storage

Field	Description	Example
Name	Friendly identifier	"GCS Production"
Bucket	GCS bucket name	"acme-ml-artifacts"
Project ID	GCP project	"acme-corp-prod"
Service Account	JSON key file	(upload or paste)

Azure Blob Storage

Field	Description	Example
Name	Friendly identifier	"Azure ML Storage"
Account Name	Storage account	"acmemlstorage"
Container	Blob container	"ml-data"
Access Key	Storage key	(from Azure Portal)

Version Control Integrations

Connect to version control for code-based workflows and GitOps deployments.

GitHub

1. Click Add Integration → GitHub
2. Choose authentication method:

- GitHub App (recommended for organizations)

- Personal Access Token (for individual use)

1. Grant access to relevant repositories
2. Save the integration

GitLab

1. Click Add Integration → GitLab
2. Enter your GitLab instance URL (for self-hosted)
3. Provide a Personal Access Token with api scope
4. Save the integration

Container Registry Integrations

Enable model containerization and deployment workflows.

Docker Hub

Field	Description
Username	Docker Hub username
Access Token	Docker Hub access token
Namespace	Default namespace for images

Amazon ECR

Field	Description
Registry URL	ECR registry URL
AWS Region	Region of ECR registry
Credentials	Use IAM role or access keys

Google Container Registry (GCR)

Field	Description
Project ID	GCP project
Location	GCR location (gcr.io, us.gcr.io, etc.)
Service Account	JSON key with GCR permissions

---

Environment Configuration

Environments help separate development, testing, and production workloads.

Understanding Environments

Environment	Purpose	Typical Configuration
Development	Experimentation and testing	Lower resources, mock integrations
Staging	Pre-production validation	Production-like, limited access
Production	Live workloads	Full resources, strict access controls

Creating Environments

1. Go to Access Control → Teams → [Your Team]
2. Click Environments tab
3. Click Create Environment

Configure each environment:

Setting	Description
Name	Environment identifier (dev, staging, prod)
Default Storage	Cloud storage integration to use
Compute Quota	Resource limits for jobs
Auto-delete Jobs	Cleanup policy for completed jobs

Environment-Specific Integrations

You can assign different integrations per environment:

┌─────────────────────────────────────────────────────────┐
│  Team: ML Research                                      │
├─────────────────────────────────────────────────────────┤
│  Environment: dev                                       │
│    Storage: dev-s3-bucket                              │
│    Registry: dev-ecr                                   │
│    Compute: 2 GPUs max                                 │
├─────────────────────────────────────────────────────────┤
│  Environment: staging                                   │
│    Storage: staging-s3-bucket                          │
│    Registry: staging-ecr                               │
│    Compute: 4 GPUs max                                 │
├─────────────────────────────────────────────────────────┤
│  Environment: prod                                      │
│    Storage: prod-s3-bucket                             │
│    Registry: prod-ecr                                  │
│    Compute: 8 GPUs max                                 │
└─────────────────────────────────────────────────────────┘

---

Access Control Configuration

Understanding RBAC

Inwire uses Role-Based Access Control (RBAC) to manage permissions:

Organization
├── Org Admin (manages org)
└── Teams
    ├── Team Admin (manages team)
    └── Members (use resources)

Managing Team Members

Inviting Members

1. Go to Access Control → Teams → [Your Team]
2. Click Members tab
3. Click Invite Member
4. Enter email and select role
5. Click Send Invitation

Role Permissions

Permission	Member	Team Admin	Org Admin
View resources	✓	✓	✓
Create jobs	✓	✓	✓
Manage datasets	✓	✓	✓
Deploy models	—	✓	✓
Manage integrations	—	✓	✓
Invite members	—	✓	✓
Delete team	—	—	✓
Manage billing	—	—	✓

API Keys

For programmatic access, create API keys:

1. Go to Access Control → API Keys
2. Click Create API Key
3. Configure:

- Name: Descriptive identifier

- Scope: Team or organization level

- Expiration: Optional expiry date

1. Copy the key immediately — it won't be shown again

> Warning: Treat API keys like passwords. Never commit them to version control.

---

Quota and Resource Management

Understanding Quotas

Quotas prevent resource exhaustion and control costs:

Quota Type	Description	Default
Monthly Records	Synthetic data records generated	Based on plan
Concurrent Jobs	Simultaneous running jobs	Based on plan
Storage	Total artifact storage	Based on plan
GPU Hours	GPU compute time	Based on plan

Viewing Quota Usage

1. Go to Settings → Usage
2. View current usage against limits
3. See historical usage trends

Adjusting Quotas (Org Admins)

If you have quota management permissions:

1. Go to Access Control → Organizations → [Your Org]
2. Click Quotas tab
3. Adjust limits per team or upgrade plan

---

Audit Logging

Inwire maintains audit logs for compliance and troubleshooting.

What's Logged

• User authentication events
• Resource creation and modification
• Job execution and status changes
• API access
• Configuration changes

Viewing Audit Logs

1. Go to Settings → Audit Logs
2. Filter by:

- Date range

- User

- Action type

- Resource type

Exporting Audit Logs

For compliance reporting:

1. Click Export in the Audit Logs view
2. Select format (CSV, JSON)
3. Choose date range
4. Download the export

---

Notification Settings

Configure how your team receives notifications:

Notification Channels

Channel	Use Case
Email	Job completions, failures, invitations
Slack	Real-time alerts, team collaboration
Webhook	Custom integrations, automation

Setting Up Slack Integration

1. Go to Settings → Notifications
2. Click Add Slack
3. Authorize Inwire in your Slack workspace
4. Select channels for different notification types

Configuring Notification Preferences

Event	Recommended Setting
Job Started	Disabled (too noisy)
Job Completed	Team channel
Job Failed	Direct message + channel
Deployment Status	Production channel
Security Alerts	Direct message

---

Best Practices

Integration Security

• Use IAM roles when running on cloud infrastructure instead of access keys
• Rotate credentials regularly (every 90 days recommended)
• Use least privilege — grant only necessary permissions
• Enable MFA for all administrative accounts

Team Organization

• Create focused teams — group by project or function
• Use descriptive names — make it clear what each team does
• Document integrations — note what each integration is used for
• Review access regularly — remove inactive users

Environment Management

• Match production — staging should mirror prod configuration
• Isolate environments — use separate credentials per environment
• Clean up dev — regularly delete old dev resources
• Document differences — note intentional variations between environments

---

Troubleshooting Setup Issues

Integration Connection Failures

Symptom: Integration shows "Connection Failed"

Solutions:

1. Verify credentials are correct
2. Check network connectivity (firewalls, VPNs)
3. Ensure required permissions are granted
4. Try regenerating credentials

Permission Denied Errors

Symptom: Users can't access expected resources

Solutions:

1. Verify user's team membership
2. Check role assignment
3. Review resource-specific permissions
4. Check if quotas are exceeded

Quota Exceeded Warnings

Symptom: Jobs fail with quota errors

Solutions:

1. Wait for quota reset (monthly)
2. Delete unused resources
3. Request quota increase from Org Admin
4. Consider plan upgrade

---

Next Steps

With your organization configured:

1. Using Inwire — Learn day-to-day workflows
2. Synthex User Guide — Set up synthetic data generation
3. Backend Services — Explore all platform services