Bugs

URGENT: Project Sharing, Guest Permissions, and Invite Management Are Broken

2mo agoCompleted

https://app.dadan.io/video/share/LKZUQn2ezmtsC8p9

This is URGENT: I’m extremely frustrated with how often I’m running into basic issues in Reloops during actual client work. I keep finding out after I send something that it either does not work as expected or the client cannot access what I intended to share.

At this point, I am spending too much time testing, reproducing, documenting, and reporting problems instead of using the product.

This needs attention now, not weeks from now after repeated follow-ups.

BUGS

1. Sharing a parent project does not properly expose its contents.

I shared the top-level Sporsho Foundation project using Share Project.

The external link takes a very long time to load, and when it finally opens, only one item from the project appears. The rest of the folders and content are not visible.

If the UI says I am sharing a project, the recipient should be able to see the project I shared. I should not have to find out from a client afterward that most of it is inaccessible.

2. Accepted invites remain under Pending Invites.

A team member has already accepted the invitation, but the invite is still showing under Pending Invites.

That state is incorrect and confusing.

3. I cannot cancel a pending invite even though I am the workspace owner.

When I try to cancel an invite, I get:

“Failed to cancel invitation, check permissions.”

I am the owner.

There is no reasonable scenario where the owner should be blocked from cancelling an invitation they created.

4. Shared project links load extremely slowly.

External project links take far too long to load. This makes the sharing problems even worse because the client has to wait just to discover that the content is missing.

FEATURE REQUESTS / MISSING FUNCTIONALITY

1. Parent project sharing needs permission inheritance.

If I share a top-level project, I need an option to include everything inside it.

Ideally, child folders and files inherit access from the parent project unless I explicitly override them.

Right now, the sharing behavior is not clear enough and does not match what a user would reasonably expect from “Share Project.”

2. Reloops needs project-specific guest access.

I need to be able to invite a client or collaborator to specific projects without giving them access to the entire workspace.

For example:

Client can access Project A. Client cannot access Projects B, C, or D.

This is basic permission control for client-facing collaboration.

WHY THIS IS URGENT

I am using Reloops with real clients right now.

These are not theoretical issues or nice-to-have improvements.

I am sending projects, clients are telling me they cannot access them, and then I have to stop working, reproduce the problem, test the link in another browser, investigate permissions, and manually fix access.

That is a direct waste of my time and it creates a bad client experience.

I have tried to be patient and supportive with Reloops, but I am genuinely getting tired of opening the product and repeatedly finding another core workflow issue.

I should not have to QA basic sharing functionality every time I send something to a client.

Please treat the bugs above as urgent. I need these looked at now, not next week.

9 comments

  1. dheeraj bhatia marked this as Completed12d ago
  2. Hi,

    Here's a new walkthrough recorded on the live site today, using real invite emails. All 29 checks passed: https://www.reloops.app/share/c0a7bad0-20a1-4447-b46a-2c6c69…

    The comments are timestamped, so you can jump to each part. Here's what's new since the last video.

    1. Accepted invites no longer stay under Pending Invites (the issue you reported) - Once someone accepts, they move to Organization Members and leave the Pending Invitations list (1:37). - Inviting someone who is already a member doesn't add them to the pending list either (7:24).

    2. A cleaner Pending Invitations list - One row per person, showing their role and how many days their link has left. - Only invites that still need action are listed: pending and expired. Cancelled invites disappear from the list instead of piling up. - Clear "Resend" and "Cancel" buttons. Resend keeps the original role, so an Admin invite stays Admin (4:49).

    3. Cancelling an invite works for the owner (the issue you reported) - The "Failed to cancel invitation" error is fixed. Cancelling takes effect right away (1:58). - A cancelled link can't be used, even if the person is in the middle of signing up when you cancel (2:50 to 4:11).

    4. Member emails in Organization Members - Each member's email now shows under their name, so you can tell people apart at a glance (1:37).

    5. Owner protection - Only an owner can change or remove an owner. An admin who tries is refused with a clear reason (6:21). - An organization always keeps at least one owner, so the last owner can't accidentally step down (6:54). - We removed a "Billing" role option that didn't work. The choices are now Owner, Admin and Member.

    6. Smoother Manage Team page - Cancelling or resending no longer makes the page jump. - Lists no longer flash the wrong content while loading.

  3. - A cancelled invite can not be used to join, even if the email was already sent. - Anyone who clicks a cancelled or expired link now sees a clear message instead of a sign-up page. - Invite links are valid for 7 days, and the app now says so. - if link got in hand of wrong email address (screenshot)

    We tested all of this on the live site with real invite emails. Here's the recording, with comments marking each step:

    https://www.reloops.app/share/6a6b7cab-a618-4acd-a8e7-f8cc19…

    • img/i_93ko80zcrylxeoaa72xv1pm0
    1. Thanks, I will check both videos out when I have a minute

  4. Here is a detailed video of the fixes, tested on the live site: https://www.reloops.app/share/f5dc0963-16ec-4252-a291-e6f0e6…

    The comments on the video are timestamped, so you can jump straight to each part.

    1. Sharing a parent project (fixed and verified): - We created a link for a few selected files first. - Then we shared the whole parent project. - A logged-out guest opening the project link now sees every folder and file, including folders nested 3 levels deep (32 of 32 files in the test). - The earlier link for the selected files keeps working on its own and doesn't carries over into the project link.

    2. Shared link loading speed (improved): - We tested the guest link on 4 network speeds, from a normal connection down to slow 3G. - On normal and 4G connections the full project shows in about 1.5 to 2 seconds. - Opening the link again is much faster because of caching. - We're rolling out one more improvement for very slow connections 3g where we have tested 400kbps speed, so the page appears right away instead of staying blank while it loads currently it loads in 28 seconds

    3. Invites and project-specific guest access (in testing): - We're building a new invite model as part of our longer-term vision for permissions. - It covers organization-level invites, plus workspace-level invites limited to specific projects. Clients would only get access to Project A, not B, C or D. - It's in testing and only released to few teams right now. I'll share a full walkthrough video here once it's verified, the same way as above.

    Thanks again for reporting everything so clearly. It's helping us get this right.

    • img/i_6a7dq5li5behob5qx2zo7t6a
  5. Has this been fixed yet?

  6. dheeraj bhatia marked this as In Progress2mo ago
  7. I will like to provide an update that We are currently working on the invite model you have described

    1. Org level invite 2. Workspace level + speciic project access.

    I will provide complete uat video here as well to show progress on testing for these.

    In the previous update we had improve the speed of loading the share link as well.

  8. Update:

    We have worked on improve the sharing experience:

    1. Share project with improved speed :

    Project Share link : https://www.reloops.app/share/project/0618d9b4-bf87-4b20-830… DEMO: https://www.reloops.app/share/08d78c8c-26b3-42e6-b89c-b556bc…

    2. Share Folder with Password and guest uploads .dng and png into the folder as anonymous user with email and name

    Folder Share Link : https://www.reloops.app/share/project/3e0f38eb-5f30-4a37-810… Password: Dheeraj2026 DEMO Link : https://www.reloops.app/share/803ef30c-db94-418e-913e-d46423…

    3. Share selection of files + folder and verification of share link that is generated for folder and project is preserved

    Share Link : https://www.reloops.app/share/project/163b9750-1d27-4504-9a5… Demo Link : https://www.reloops.app/share/a55ab2f8-1aa5-473c-a62b-56484b…

    Rest of the fixes are under way and are also being tested

  9. We’ve traced the issue with the project sharing behavior.

    The problem appears to happen when a share link has previously been created for a specific selection of files. That selected-file sharing link can incorrectly carry over into the project share link.

    Video: https://www.reloops.app/share/3e00a81e-4387-4814-9ff0-d0a3e4…

    My sincere apologies for this. I completely understand how frustrating this is, especially when you’re sharing projects directly with clients.

    I am taking all feedback seriously and everything from the list above is being taken urgent.

    We’re actively working on a fix now, and I’ll update you right here as soon as we have progress or the fix is deployed.

  10. dheeraj bhatia marked this as In Review2mo ago
  11. Thanks for taking the time to write all of this out. I completely understand the frustration, especially when these issues are affecting work you’re already doing with clients.

    I’m going to make sure these are looked at immediately. The project sharing behavior, pending invite state, invite cancellation permissions, and slow shared links all need to work reliably, and I’ll make sure they’re addressed as a priority.

    I also agree with your points around permission inheritance and project-specific guest access. Sharing a project should behave the way you’d naturally expect, without requiring you to double-check everything before sending it to a client.

    I’m sorry you’ve had to spend this much time testing and reporting issues instead of just using Reloops. I appreciate you calling these out clearly, and I’ll make sure we get them resolved.