Projects & Team Collaboration

Learn how to structure your organization, manage applications, and collaborate effectively in Aperture’s web-to-native deployment platform.

Organization Structure

Every Aperture account belongs to at least one organization, which serves as the container for all resources:

Organization Components

• Members (Users with access) Individual users who can access the organization resources based on their assigned roles.

• Teams (Groupings of members) Collections of users with similar responsibilities, like Development, QA, or Operations teams.

• Applications (Web and Native) The web applications you want to deploy and the native applications that will receive them.

• Deployments Records of the deployment processes that deliver web content to native applications.

Why Team Structure Matters

Proper team organization in Aperture delivers significant benefits:

Improved Security

Limit sensitive actions like deployments to appropriate team members, reducing risk of unauthorized changes.

Reduced Deployment Risk

Ensure changes are reviewed by the right people before they’re released to your users.

Clear Accountability

Know who made what changes when issues arise, making troubleshooting faster and more efficient.

Workflow Efficiency

Streamline approvals and handoffs between teams, reducing bottlenecks in your deployment process.

Setting Up Your Organization

To create and configure your organization effectively:

1. Define your organization Navigate to Settings → Organization and configure your organization name, description, default timezone, and billing information.

   Why it matters: Your organization settings affect how timestamps are displayed, when scheduled deployments occur, and other system-wide behaviors.

2. Plan your team structure Before creating teams, consider how your company is organized, who needs access to which applications, what deployment responsibilities exist, and your security requirements.

3. Create teams Navigate to Settings → Teams → New Team and specify the team name, description, team lead/manager, and initial members.

   Why it matters: Well-structured teams simplify permission management and create clear boundaries of responsibility.

4. Assign application access to teams For each web or native application, navigate to Access → Manage Team Access and specify which teams should have access and at what permission level.

Roles and Permissions

Roles define what actions members can perform in your Aperture organization:

Default Roles

Aperture includes three default roles that are available in all plans:

• Owner: Full administrative access
• Admin: Can manage most aspects except organization settings
• Member: Basic access to organization resources

Custom Roles (Pro/Enterprise)

Pro and Enterprise customers can create tailored permission sets:

• Deployment Manager: Can create and manage deployments but not applications
• QA Specialist: Read-only access plus ability to create cohorts for testing
• Analytics Viewer: Read-only access to performance and user metrics

Custom roles allow for precise permission allocation, following the principle of least privilege while still enabling teams to work effectively.

Collaboration Workflows

Aperture provides several tools to streamline team collaboration during the deployment process:

Deployment Approval Workflow (Enterprise)

Create structured review processes for deployments:

Example workflow:

1. Developer creates deployment
2. QA team reviews and approves
3. Operations team gives final approval
4. Deployment executes automatically

Enterprise plan only

Team-Based Application Access

Configure which teams can access each application:

• Map primary owner team to each application
• Identify secondary teams with usage needs
• Determine appropriate permission level for each
• Configure notification settings for deployments

Scaling Your Organization

As your organization grows, your Aperture setup should evolve:

Startup Phase (2-10 members)

• Single team with clearly defined roles
• Simple permission structure
• Direct communication for deployments

Growth Phase (10-50 members)

• Multiple teams by function
• Role-based permissions
• Structured deployment process

Enterprise Phase (50+ members)

• Teams organized by product or business unit
• Custom roles with granular permissions
• Formalized approval workflows
• Audit logging and compliance tracking

Managing Multiple Applications

As your application portfolio expands, organizing them effectively becomes critical:

Organize applications logically

Consider structuring applications by:

• Business function
• User segment
• Technology stack
• Development team

Implement consistent tagging

Navigate to Web/Native Application → Settings → Tags and apply consistent tags to group related applications.

Configure default settings templates

Create templates for deployment configurations, permission sets, and notification rules to maintain consistency.

Best Practices for Team Collaboration

• Document Your Permission Strategy Create clear documentation that explains what each role is allowed to do and why.

• Implement Regular Permission Reviews Schedule quarterly reviews to remove permissions from users who no longer need them.

• Create Clear Escalation Paths Establish procedures for emergency deployments and handling failed deployments.

• Train Your Team on Aperture Ensure all team members understand how to interpret deployment metrics and their responsibilities.