A small, temporary project team can run a lightweight file-sharing workflow using ShareIt Online’s Group Chat to discuss and re-share active files across desktop and mobile browsers, without installing any software. The key is to treat the Group Chat as a persistent, encrypted message board for links, while keeping the actual files in ShareIt’s My Files storage under their own expiry and password controls. This approach works well for engagements lasting a few weeks, but teams should plan a migration trigger to a full collaboration suite when the project outgrows plain-text chat or needs granular permissions.
The Workflow: Link-Based Collaboration in a Browser
The workflow assumes a project lead, two contractors, and a client who need to exchange design files, specification sheets, and status updates over a four-week sprint. No one wants to install an app, and the client should not need an account.
Step 1: Set up the Group Chat. The project lead visits ShareIt.onl, signs in with a Google-connected account, and creates a Group Chat. The lead then invites the two contractors by sharing the invitation link. All three members must sign in with a Google account to join. The client does not join the chat.
Step 2: Upload and share files. When the lead has a batch of design files, they upload them via ShareIt’s basic share flow. A single share can hold up to 100 files and 3 GB total. The lead sets a link expiry (e.g., 7 days) and optionally enables password protection or a one-time link. Once the upload finishes, ShareIt supplies a web link and QR code. The lead copies the link.
Step 3: Post the link in Group Chat. The lead pastes the link into the Group Chat. The chat’s message text, filenames, and any new chat attachment copies are encrypted and decrypted in each member’s browser using AES-256-GCM. ShareIt stores the ciphertext for synchronization but cannot read it. The original files remain in the lead’s My Files storage, separate from the chat copies, and retain their normal ShareIt controls (expiry, password, one-time use).
Step 4: Recipients download. Contractors open the link in their desktop or mobile browser. If the lead set a password, the contractor must enter it. The file downloads directly. No account is needed to download.
Step 5: Re-sharing and updates. If a contractor needs to send a revised file, they can create a basic share without an account and post the new link in Group Chat. A member who uses My Files can also keep files in the free 20 GB storage and issue a fresh link after an earlier link expires. The chat serves as a plain-text log of which link corresponds to which version.
Step 6: Collecting files from the client. To receive files from the client without requiring them to sign up, the lead uses ShareIt’s Request Files feature. The lead signs in with Google and creates an inbox link set to last 7 or 30 days. The client clicks the link, uploads up to 100 files or 3 GB, and submits. The client needs no account. Received files are kept for 7 days, and each time the lead downloads a file, that file’s retention extends by 24 hours. Note that Request Files inbox links do not support password protection.
Governance Boundaries
This workflow has clear limits that the project lead should communicate to the team upfront.
- Group Chat is plain text. There are no calls, threads, bots, message editing, or push notifications. If the team needs to discuss multiple workstreams in parallel, ask members to prefix messages with a project code such as “[DESIGN]” or “[SPEC].”
- Google-connected account required for chat members. Anyone who joins Group Chat must sign in, so keep nonmembers on the basic share or Request Files workflow.
- My Files items are separate from chat encryption. Group Chat’s browser-side encryption covers message text, filenames, and new attachment copies. Original items in My Files retain their normal ShareIt controls.
- Keep your own project archive. Treat the chat as a coordination channel and retain local or approved cloud backups of critical files.
Migration Triggers: When to Move to a Full Suite
The lightweight workflow is ideal for short-lived engagements, but the project lead should watch for these triggers and migrate to a full collaboration suite when they appear.
- The project becomes long-running. Plain-text chat can become unwieldy over time. Consider moving to a platform with threaded conversations, file versioning, and calendar integration.
- The group becomes difficult to coordinate. ShareIt.onl states no member limit here, but larger teams may need moderation and organization features that this plain-text chat does not provide.
- The client needs to participate in discussions. Chat members need Google-connected accounts. If the client must comment on files, a shared Google Drive folder with viewer, commenter, or editor permissions may be simpler.
- Files exceed 3 GB per share or 100 files per batch. A large media project may hit those limits. SwissTransfer permits up to 50 GB per transfer without registration, with availability up to 30 days and optional password protection. It encrypts in transit and at rest, though it is not end-to-end encrypted.
- End-to-end encryption is required for every file. ShareIt’s Group Chat encryption covers chat content and new chat attachment copies; My Files items remain separate under normal ShareIt controls. Compare Wormhole or Proton Drive when end-to-end encryption for files is the deciding requirement.
Common Mistakes and How to Avoid Them
- Choosing the wrong expiry. Set an available expiry period that matches the project timeline.
- Assuming the client knows the Request Files limits. Explain the 100-file and 3 GB per-delivery ceilings in a brief instruction note.
- Treating Group Chat as a permanent archive. Download important files to local storage or an approved cloud drive before the project ends.
- Confusing My Files with chat attachments. Original My Files items remain separate from new chat attachment copies and follow their normal controls.
Practical Advice for the Project Lead
Start with Group Chat and Request Files for the client. On day one, post the project’s file-naming convention and the client’s inbox link, then ask members to save those instructions somewhere easy to find. Set a calendar reminder to download client submissions before the 7-day retention expires. When the project ends, save the files you need and remove or let expire any links you no longer want active.
