Planning Your Distribution Strategy

Here's the breakthrough about distribution: Portals solve both internal collaboration and external sharing. Whether you need to collaborate with team members on curated content or share with agencies, partners, press, prospects, or clients, Portals provide controlled, trackable, branded distribution—functioning as everything from internal review spaces to Digital Sales Rooms to press kits to brand asset libraries.

Distribution is where your carefully organized assets meet both your team and the outside world. You've planned your metadata, designed your folder structure, and configured permissions—now you need to share those assets securely and efficiently with the right people at the right time.

This guide will help you design a distribution strategy that works for both internal collaboration and external sharing, aligned with your organization's workflows and security requirements.

The Distribution Problem

Poor distribution planning leads to chaos and security risks:

Email attachment hell – Large files bouncing back, version confusion, no tracking of who has what, assets scattered across inboxes with no central control.

Uncontrolled sharing – Links shared via consumer tools (Dropbox, WeTransfer, Google Drive) with no tracking, no expiration, no understanding of who accessed what or when.

Too many platform accounts – Creating user accounts for every external partner, agency, or vendor creates permission complexity, security risks, and administrative overhead. Each account needs configuration, monitoring, and eventual deactivation.

No visibility or tracking – When assets leave your system via uncontrolled channels, you lose all visibility. Who downloaded what? Are partners using your assets? Which materials are most valuable?

Brand assets in unauthorized hands – Without proper distribution controls, sensitive or unapproved content ends up shared externally, potentially damaging your brand or violating agreements.

Key Takeaway: Most organizations over-complicate distribution. Portals now handle both internal collaboration and external sharing, eliminating the need for complex workarounds. Distribution problems are usually solved by using the right portal type for the right scenario.

Understanding Your Distribution Needs

Before configuring any distribution methods, map out who needs to share assets with whom, and under what circumstances.

Internal Distribution

Who needs to collaborate internally?

What do they need to share?

Internal distribution methods:

External Distribution

Who are your external recipients?

What are common external sharing scenarios?

External distribution method: External Portals for nearly all scenarios. They provide controlled access without creating user accounts, maintaining your permission structure, or training external people on your platform.

Control Requirements

What level of control do you need over distributed assets?

These control requirements directly inform your Portal configuration strategy.

Quick Win: List your top 5 distribution scenarios right now—both internal (team reviews, cross-department collaboration) and external (agencies, partners, press contacts, clients). For each one, answer: Internal or external portal? What do they need? Can they download? Should this be time-limited? This becomes your initial Portal plan.

Distribution Methods in Data Dwell

Data Dwell provides multiple distribution methods, each suited to different scenarios. Understanding when to use each method is key to effective distribution planning.

Portals: Primary Distribution Method (Use This Most)

Portals are configurable containers for sharing and distributing digital assets. They support both internal collaboration and external sharing through two portal types: Internal Portals and External Portals.

Internal Portals

Internal Portals are accessible only to authenticated workspace members. They do not generate a public link and are ideal for internal collaboration and review workflows.

Key capabilities:

Best for:

External Portals

External Portals generate a public link that can be shared with anyone outside the workspace. They provide controlled, trackable, and branded content delivery without requiring external users to have platform accounts.

Key capabilities:

Best for (almost everything external):

Critical insight: Portals eliminate the need for creating user accounts, configuring permissions, training external users, and managing account lifecycles for external parties. They're simpler, more secure, and provide better tracking than platform access.

Platform Access: Full Internal Collaboration

Granting user accounts with appropriate permissions is the method for users who need to work within the platform. Access is governed by your permission structure—users see only the folders and assets their permissions allow. In smaller organizations, internal users may have access to everything. As organizations grow, access is typically siloed by department or function (e.g., marketing users access marketing and brand folders, sales users access sales materials). The right approach depends on your folder structure and permission strategy.

Best for:

NOT appropriate for:

Remember: Platform access is governed by your permission structure (see Planning Permissions article). Before creating a user account for someone, ask: "Could an Internal or External Portal solve this instead?" The answer is often yes.

Showcases: Public Image Galleries

Showcases create public or semi-public image galleries for broad access without individual recipient tracking.

Best for:

Note: Showcases currently connect to Dwellings to manage displayed content. An upcoming update will change Showcases to use filters instead, providing more flexible content selection. If you need to track specific recipients or relationships, use External Portals instead.

Public Links

Direct links to individual image assets that can be embedded in other platforms or systems.

Best for:

Note: For person-to-person sharing, even of single assets, use Portals instead—they provide better tracking of who accessed the content. Public links are primarily for technical platform integrations rather than direct sharing with individuals.

API Integration

Programmatic access for connecting Data Dwell to other platforms for automated distribution.

Best for:

Quick Win: Review your current distribution methods. How many external people have platform user accounts? For each one, ask: "Could this be an External Portal instead?" You'll probably identify accounts that should be converted to Portal access.

Planning Your Portal Strategy

Since Portals are the primary distribution method for both internal and external use, planning them thoughtfully is critical. Think of Portals as workspaces that need the same strategic planning as your internal folder and permission structure.

Portal Types and Purposes

Different scenarios need different Portal configurations. Define your Portal types based on use cases:

Internal Review Portals

Digital Sales Room Portals

Partner/Vendor Portals

Lead Generation Portals

Agency/Contractor Portals

Press/Media Portals

Client Review Portals

Retail/Distributor Portals

Quick Win: Review the portal types above. Which 3-4 types match your immediate needs? Write down one real scenario for each type. These become your first portals after launch.

Portal Naming and Organization

Like folders, Portals benefit from clear, consistent naming conventions that make them easy to find, manage, and audit.

Consider naming patterns like:

Consistent naming makes Portals easier to find, manage, and audit. The platform also provides search capability in the portal list and filters to find your own portals or portals assigned to specific accounts. When you have 50+ portals, combining good naming conventions with search and filters keeps everything manageable.

Portal Content Strategy

Portals provide flexible content management with centralized control. You add folders and assets directly to each portal, managing what's visible to recipients from the portal record itself.

How portal content works:

Content management approaches:

Approach 1: Add Specific Folders

Add entire folders to portals. Content within those folders automatically stays current as you update the platform.

Approach 2: Curate Individual Assets

Select specific assets from anywhere in your platform to add to the portal.

Approach 3: Portal Collections

Create collections within the portal to organize content into logical groups, each with a custom thumbnail.

Approach 4: Hybrid

Combine approaches—add some folders for stable content, curate specific assets for special cases, and organize with Portal Collections.

Central control principle: All portal content is managed from the portal record itself. This centralized approach makes it easy to see what's shared with each recipient, update content, and maintain security.

Portal Access Settings (Critical Planning Decision)

Access settings vary between Internal and External portals. Getting these settings right is critical for security and tracking.

Internal Portal Access

Internal portals use workspace-based access:

External Portal Access

External portals offer multiple access control options:

Access Restriction Options:

Expiration Dates:

Allow Download Setting:

Allow Share Setting:

Decision framework for external portals:

Common mistake: Using open access by default without considering the access control options. Start with appropriate restrictions and only loosen controls when justified for that specific portal and recipient.

Portal Metrics and Tracking

External portals include built-in engagement metrics:

Use these metrics to:

Quick Win: Plan to review portal metrics monthly. Create a simple tracking spreadsheet: Portal Name, Unique Visitors, Downloads, Last Activity. This helps identify which relationships need attention.

Portal Isolation for Tracking

Portal isolation strategy depends on your use case—whether you're managing known relationships or generating new leads.

Relationship Tracking: One Portal Per Stakeholder

For known relationships (partners, agencies, specific clients or prospects), creating separate portals for each distinct stakeholder enables precise tracking and relationship insights.

The problem with shared portals: One "Agency Partners" portal shared with 10 different agencies means you can't tell which agency is downloading which assets, which partners are most engaged, or which relationships need attention.

Better approach for relationships: Create separate portals for each distinct stakeholder or relationship, even if they're accessing similar content. Yes, this means more portals, but it provides invaluable tracking and relationship insights.

Example:

❌ Bad: One "Q2 Campaign - Agency Partners" portal shared with Agency A, Agency B, and Agency C

✅ Good: Three portals – "External - Agency - Agency A - Q2 Campaign", "External - Agency - Agency B - Q2 Campaign", "External - Agency - Agency C - Q2 Campaign"

Portal isolation for relationships enables you to:

Lead Generation: Broad Access Portals

For lead generation scenarios, a different approach makes sense. When you want to capture emails from unknown prospects, use portals with "any email" access.

Lead generation portal approach:

Best for:

Decision framework:

Both approaches have value—the key is choosing the right one for your use case.

Account and Contact Linking (Recommended for External Portals)

Linking External Portals to Accounts and Contacts is optional but strongly recommended when sharing to specific relationships. This practice significantly improves tracking and relationship management.

When to link Account and Contact:

When linking may not be necessary:

Why linking is recommended for known relationships:

Make Account and Contact linking a standard part of your portal creation process for all relationship-based external portals.

The Relationship Between Distribution and Permissions

Distribution and permissions are interconnected. Your permission structure determines who can create and manage Portals, and what content can be shared.

Who Can Create Portals?

Like folder creation, Portal creation should be limited to users who understand distribution strategy, security requirements, and brand guidelines.

Typical Portal creators:

Configure Portal Manager Application Role (see Planning Permissions article) for users who need to create and manage portals. Avoid allowing all users to create Portals—this can lead to uncontrolled sharing, inconsistent configurations, and security risks.

Portal Content and Folder Access

Users creating Portals can only link to folders and assets they have permission to access. This is a critical security feature that prevents accidentally sharing content the Portal creator shouldn't be distributing.

Planning consideration: If Marketing managers should create portals for marketing assets but not access HR or Finance content, your folder structure and permissions must enforce these boundaries (see Planning Permissions and Planning Folder Structure articles).

Best practice: Create dedicated "Approved for External Distribution" or "External Sharing" folders that contain only pre-approved, externally shareable assets. Portal creators can safely link to these folders without risk of sharing unapproved or confidential content.

Distribution Decision Framework

Always ask: What type of access is needed? Here's how to decide:

Use Platform Access (create user account) when:

Use Internal Portals when:

Use External Portals when:

The default for external people should be External Portals. Only create platform accounts when portals truly can't meet the need—which is rare.

Quick Win: Write a one-page decision guide: "Platform Access vs. Internal Portal vs. External Portal – When to Use Each." Include the criteria above and 3-5 examples of each. Share this with anyone who can create user accounts or portals.

Common Distribution Mistakes

Creating User Accounts Instead of Using Portals

This is the most common and most costly distribution mistake. Every unnecessary user account creates permission complexity, security risk, and administrative overhead.

The problem: Admins default to creating user accounts because that's familiar from previous systems, not recognizing that Portals solve external sharing more elegantly.

Better approach: Default to External Portals for all external recipients. Create user accounts only when external people truly need to contribute content or participate in workflows.

Using Only External Portals for Internal Collaboration

The problem: Teams create external portals for internal review workflows, missing the benefits of Internal Portals.

Better approach: Use Internal Portals for internal collaboration. They integrate with your permission structure and don't require managing external access controls.

Poor Access Settings Configuration

The problem: Using open access or overly permissive settings on every external portal without considering the access control options reduces security and tracking effectiveness.

Better approach: Choose appropriate access restrictions based on the use case. Use email restrictions for known relationships, password protection for simple gatekeeping, and "any email" for lead generation. Document why each setting is chosen.

Missing Expiration Dates

The problem: External portals created for specific projects or time periods remain accessible indefinitely, creating security risks.

Better approach: Set expiration dates on project-based, campaign-specific, or time-sensitive external portals. Review and extend as needed rather than leaving access open indefinitely.

Creating Portals Without Isolation

The problem: One portal shared with multiple different stakeholders destroys tracking and relationship insights.

Better approach: Create separate external portals for each distinct stakeholder relationship. Yes, this means more portals, but the tracking value is immense.

No Account and Contact Linking

The problem: Creating external portals without linking them to Accounts and Contacts when sharing to specific relationships means you lose valuable tracking and analytics.

Better approach: Link Accounts and Contacts when creating external portals for known relationships. For lead generation portals, focus on capturing visitor emails instead.

Not Using Portal Metrics

The problem: Creating portals without monitoring engagement means you don't know if recipients are using the content or which assets are most valuable.

Better approach: Regularly review portal metrics (unique visitors, total visits, total downloads). Use this data to inform relationship management and content strategy.

Ignoring Portal Collections

The problem: Large portals become difficult to navigate when all assets are dumped together without organization.

Better approach: Use Portal Collections to organize content into logical groups with custom thumbnails. This improves the recipient experience and makes content easier to find.

Creating Portals Without Strategy

The problem: Admins create Portals reactively without considering naming, settings, or long-term management.

Better approach: Define Portal types and naming conventions upfront. Create Portals deliberately based on established templates and patterns.

Permanent Access Without Review

The problem: Portals created for specific projects often remain active long after they're needed.

Better approach: Review external Portals quarterly. Deactivate or remove Portals for completed projects, departed contractors, or inactive relationships.

Sharing Unapproved Content

The problem: When Portals link to folders without clear approval processes, work-in-progress or unapproved assets can accidentally be distributed externally.

Better approach: Create designated "Approved for External Distribution" folders. Never link external portals to working folders with mixed approval states.

Designing Your Distribution Structure

Map Distribution Scenarios

Before creating any Portals, document your common distribution scenarios:

  1. List all internal collaboration needs (reviews, cross-team sharing, staging)
  2. List all external recipient types (partners, agencies, press, prospects, clients, etc.)
  3. For each scenario, define what they need access to and why
  4. Determine appropriate portal type (internal or external)
  5. Determine appropriate access settings
  6. Identify whether this is ongoing or project-based
  7. Estimate how many portals of each type you'll need

Quick Win: Create a simple table right now with columns: Scenario, Internal/External, Access Control, Download?, Duration. Fill in 10 rows representing your real distribution needs. This becomes your portal planning document.

Create Portal Templates

Based on your scenarios, define 4-6 Portal templates (patterns) you'll use repeatedly:

Example Portal Templates:

Templates make Portal creation faster, more consistent, and reduce configuration errors.

Designate Portal Managers

Identify who in your organization should create and manage Portals:

Configure the Portal Manager Application Role (see Planning Permissions article) for these designated users. Limit Portal creation permissions to 5-10 people in most organizations.

Create External Distribution Folders

If you'll link external Portals to folders, consider creating dedicated folders for external distribution:

This makes it easy to connect external Portals to pre-approved content and reduces the risk of sharing unapproved assets.

Plan for API Distribution

If you'll integrate Data Dwell with other platforms (CMS, e-commerce, marketing automation), document:

Implementation Strategy

Phase 1: Start with Core Distribution Needs

Begin with your most common distribution scenarios. Don't try to solve every possible sharing need on day one.

Typical starting points:

Launch with these core portals and gather feedback before expanding. Validate your portal templates and access settings with real usage.

Quick Win: Create your first 4 portals this week. Pick one internal review scenario, one partner, one agency, and one prospect or press contact. Configure them according to your templates. Get feedback from recipients about the experience.

Phase 2: Monitor and Refine

After launch, track Portal usage closely:

Use this data to refine your Portal templates, access settings, and distribution strategy. Schedule monthly reviews for the first quarter after launch, then quarterly thereafter.

Phase 3: Scale and Systematize

As distribution needs grow:

Documentation and Governance

Document your distribution strategy to ensure consistency and security:

Distribution Policy Document should include:

Quick Win: Create a one-page "Portal Quick Reference" document right now with: (1) Portal types and when to use each, (2) Access control options, (3) Naming convention, (4) Account/Contact requirement for external portals. Share with anyone who can create portals.

Your Next Steps

  1. Map distribution scenarios – Document both internal collaboration needs and external sharing requirements
  2. Define Portal types – Create 4-6 Portal templates for common use cases (both internal and external) with documented access settings
  3. Establish naming conventions – Decide how Portals will be named and organized for easy management
  4. Create external distribution folders – Designate folders with pre-approved, shareable content for external portals
  5. Designate Portal managers – Limit who can create and manage Portals (configure Portal Manager Application Role)
  6. Set access settings framework – Document decision criteria for access restrictions, expiration, download, and share controls
  7. Emphasize portal isolation – Train portal managers that separate external stakeholders need separate portals for tracking
  8. Require Account/Contact linking – Make this standard practice for external portals shared with known relationships
  9. Plan metrics review – Establish process for reviewing portal engagement metrics
  10. Document distribution policy – Write clear guidelines for when and how to use each distribution method
  11. Create initial Portals – Start with 4-6 Portals for your highest-priority scenarios (mix of internal and external)
  12. Plan for review – Schedule monthly activity reviews initially, then quarterly audits

Remember: distribution is an extension of your permission and folder strategy. Portals now handle both internal collaboration and external sharing. Plan your distribution with the same care as permissions and folders, and ensure all three systems work together cohesively.

Related Articles

Get in touch
for a demo

Information

+354 525 3535Bjargargata 1102 Reykjavikdatadwell@datadwell.com