Capability

Sharing and distribution

Share items through links, users or groups and provide original or transformed downloads.

Overview

Share items through links, users or groups and provide original or transformed downloads.

Sharing and distribution interface in Apification
Separate distribution modes

Choose authenticated collaboration, reusable groups or deliberate public visibility instead of using one link for every audience.

Access for users and groups

Grant access to individual Apification users or reuse groups across resources that share the same audience.

Public views adapted to the service

Present files, landings, forms and interactive services through the public experience intended for their content.

Features

What Sharing and distribution can do

01

Separate distribution modes

Choose authenticated collaboration, reusable groups or deliberate public visibility instead of using one link for every audience.

02

Access for users and groups

Grant access to individual Apification users or reuse groups across resources that share the same audience.

03

Public views adapted to the service

Present files, landings, forms and interactive services through the public experience intended for their content.

04

Controlled original downloads

Deliver the stored source with a readable filename while keeping the managed Cloud resource unchanged.

05

On-demand transformed downloads

Offer a compatible output format during delivery without replacing the original or keeping an unnecessary permanent copy.

06

Access that can be withdrawn

Change visibility, users or groups when a collaboration ends while the owner retains the source and its history.

07

Permission-aware recipient experience

Expose only the view, participation or download actions allowed by the resource type and its configuration.

08

Distribution without duplication

Reuse one controlled resource for internal teams, external audiences and multiple delivery formats.

Distribution path

Choose the audience before choosing the link

Each delivery starts with an access decision and keeps control with the resource owner.

  1. 01

    Select audience

    Define whether access is for users, a reusable group or a public visitor.

  2. 02

    Set experience

    Choose the service view, original file or compatible transformed output.

  3. 03

    Distribute

    Provide the appropriate Cloud access or public destination.

  4. 04

    Update or withdraw

    Change access later without replacing or duplicating the source resource.

Operational detail

How Sharing and distribution works in practice

Sharing separates internal collaboration, public visibility and file delivery so each resource can reach the right audience without granting broader access than necessary.

Visibility is explicit

Items start private. Public access is enabled deliberately and remains separate from access granted to authenticated Apification users.

Users and reusable groups

Grant access to individual users or maintain groups for teams and customers that need the same permissions across several resources.

Service-specific public views

Published landings, forms, events, files and other services open through the view designed for their content rather than a generic download page.

Original file delivery

The download tab can provide the stored source with a readable filename and timestamp while preserving the Cloud item.

Transformed downloads

Compatible files can be converted during delivery, reusing File Transformer formats without forcing the owner to create permanent copies first.

Access can be withdrawn

Changing visibility, users or groups updates future access while the owner keeps control of the original resource and its history.

Frequently asked questions

Questions about Sharing and distribution

No. User and group access is for authenticated collaboration. Publishing exposes the configured public view or link without granting account-level access.

No. The requested format is generated for delivery and the source remains the stored Cloud resource.

Yes. Reusable groups avoid assigning the same users individually to every item.

That depends on the item type and granted access. The interface only exposes the view, download or service actions allowed by its configuration.