3d ago

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

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.

In Progress