Tell us how we could make the product more useful to you. We URGE you to use the Pelcro Discovery GPT to help structure your thoughts and recommend a feature request that will be quickly digested by our team!
Have something to say?
Disable Gift Creation in the Customer Portal
🔍 Problem Statement Publishers who no longer offer gifting can hide the gift option during plan selection and checkout, but customers can still create new gifts through the customer portal (Gifts > Add a gift). 💡 User Story As a publisher, I want to disable gift creation across all entry points, including the customer portal, so that customers can’t create new gifts while still having access to their existing ones. 🎯 Definition of Done (DoD) ✔ Gift creation can be disabled in the customer portal (Gifts > Add a gift). ✔ Direct access to the gift creation flow is blocked when gift creation is disabled. ✔ Existing gifts, including recipient details and shipping addresses, stay accessible to customers. ✔ This change will impact UI, specifically the Gifts section of the customer portal and the gift creation flow.
Planned
Allow pinning Default UI Version to the newest release without automatic upgrades
🔍 Problem Statement As a site admin, I can only adopt the newest UI version by selecting "Latest," which results in automatic future upgrades without consent. 💡 User Story As a site admin, I want to pin my site to the newest UI version, so that I get current features without automatic future upgrades. As a site admin, I want "Latest" to remain available, so that I can still opt into automatic upgrades. 🎯 Definition of Done (DoD) ✔ Given the Default UI Version setting, when an admin opens the dropdown, then the newest release (currently 3.0) is listed as a pinnable option separate from "Latest (3.0)". ✔ Given a site pinned to 3.0, when a newer UI version is released, then the site continues serving 3.0 until an admin changes the setting. ✔ Given a site set to "Latest", when a newer UI version is released, then the site serves the new version, unchanged from current behavior. ✔ Given a new UI version is released, when it is published, then it appears in the dropdown as a pinnable option without manual configuration. ✔ Given a site settings API request, when the UI version is read or updated, then the API accepts and returns either a specific version or "latest". ✔ This change will impact UI, API, and SDK, specifically the Site Settings Default UI Version dropdown, [clarify site settings endpoint/field], and the UI bundle version loader. ✔ This solution will include the following limitations: no notification of new UI releases; no automatic migration of existing "Latest" sites to a pinned version; no per-page or per-environment version selection.
Planned
Utilization2: Optimize AI Home recommendations
🔍 Problem Statement Currently, the Pelcro homepage provides business performance insights and AI-powered recommendations, but these do not fully leverage the customer activity data already available within Pelcro. Clients can access information about customer behavior, traffic sources, page visits, and device engagement, but may not know how to interpret this data or use it to improve conversions and revenue. Additionally, homepage recommendations should do more than promote unused Pelcro features. They should proactively identify meaningful business opportunities, explain their potential impact, and guide clients toward actionable next steps using AI Harness or relevant Pelcro functionality. 💡 User Story As a Pelcro admin, I want to receive personalized, actionable AI-powered recommendations on my homepage based on my account activity, customer behavior, business performance, and feature utilization, so that I can identify revenue opportunities, understand customer engagement, and discover relevant Pelcro features without having to analyze the data manually. 🎯 Definition of Done (DoD) 1. Homepage Recommendation Prioritization Given an account has urgent financial issues, such as significant revenue decline or past-due MRR, prioritize these insights over promotional recommendations. Given no urgent financial issues exist, prioritize relevant feature adoption opportunities and actionable customer activity insights based on their potential business impact. Given customer activity data indicates opportunities to improve conversions or revenue, prioritize those insights over lower-impact feature promotions. Given additional recommendations are available, display them below the top recommendations. Given a recommendation becomes irrelevant or its suggested action is completed, remove it and replace it with the next eligible recommendation. Avoid displaying multiple recommendations that communicate the same issue or opportunity. Recommended Sorting of Homepage Cards Priority Card Where to Display Reason 1 Identify High-Traffic, Low-Conversion Pages Top row Highlights opportunities to turn existing traffic into more subscriptions and revenue 2 Enable Apple Pay / Google Pay Top row Direct checkout improvement when supported but not enabled 3 Create Your Revenue Growth Plan Top row Drives AI Agent engagement and promotes AI Billing 4 Identify Your Top Referral Sources Second row, dynamically Helps clients understand which acquisition channels drive valuable traffic and conversions 5 Discover Your Top-Converting Pages Second row Helps clients identify which pages generate the most subscriptions and revenue 6 Analyze
Planned
Utilization: Optimize AI studio recommendations
🔍 Problem Statement Currently, AI Studio displays a limited set of suggested prompts focused primarily on basic screen customization, such as changing brand colors, rewriting text, and modifying navigation. These suggestions do not fully demonstrate the potential value of AI Studio to clients, particularly when it comes to improving checkout conversions, reducing subscription cancellations, and enhancing the overall customer experience. We want to introduce more engaging, business-oriented predefined prompts that encourage clients to explore AI Studio and discover how they can customize their storefronts. 💡 User Story As a Pelcro admin, I want to see relevant, predefined prompts when opening AI Studio, so that I can quickly discover useful customization opportunities and make improvements without having to write prompts from scratch. 🎯 Definition of Done (DoD) 1. Add New Suggested Prompts Add the following predefined prompts to the Suggested section of AI Studio: Checkout Conversion Show a coupon when someone hesitates at checkout. Make my checkout buttons more eye-catching. Subscription Retention Offer a coupon before someone cancels their subscription. Highlight my most popular subscription plan. Product Layout & Design Display my products side by side instead of vertically. Add a "Most Popular" badge to one of my plans. Given an admin opens AI Studio, when the Suggested section loads, then the predefined prompts should be displayed as clickable suggestions. Given an admin clicks a suggested prompt, then the prompt should be automatically populated into the AI Studio conversation and submitted for processing. The admin should be able to modify or refine the requested changes through follow-up messages. Existing suggested prompts should remain available unless intentionally replaced.
Planned
Support toll free numbers in iVR
Currently, Pelcro's Twilio integration does not support using toll-free phone numbers for IVR configurations. This limits clients who want to use toll-free numbers for customer support, particularly those who need to maintain existing customer-facing numbers or test their IVR before going live. 💡 User Story As a Pelcro admin, I want to configure toll-free phone numbers through Twilio, so that customers can reach the IVR using a toll-free number instead of a regular local number. 🎯 Definition of Done (DoD) 1. Toll-Free Number Support Support adding and configuring Twilio toll-free numbers for Pelcro IVR. Allow toll-free numbers to be assigned to the appropriate Pelcro account. Ensure the integration supports properly provisioned and eligible Twilio toll-free numbers. 2. IVR Call Routing Given a customer calls a configured toll-free number, route the call to the correct Pelcro IVR flow. Ensure existing IVR functionality works with toll-free numbers, including menu navigation and call transfers where supported. Ensure existing local phone number configurations remain unaffected.
Planned
Add Total Draw, Full Bundles and Loose Copies per Carrier Route to Bundle Top
Problem Statement Delivery team need the copy count, full bundles and loose copies printed on each carrier route page of the Bundle Top PDF, so they can bundle a carrier's papers straight from the page. User Story As an admin, I want each carrier route page of the Bundle Top to show the route's total draw, full bundles and loose copies, so the bundling team knows exactly how many bundles and loose papers to prepare for that carrier. Definition of Done (DoD) Given a Bundle Top PDF is generated, each carrier route page shows Total draw, Full bundles and Loose copies for that route, clearly labelled together in the route header area. Full bundles and loose copies are calculated from the route's total draw (copies delivered this run, stops excluded) using the formula above. The bundle size is configurable per account, set from the same Pelcro admin Bundle Top settings that hold "Include all quantities" (BundleTopController / StoreBundleTopRequest), and defaults to 30 when not set. When the total draw is less than the bundle size, the page shows 0 full bundles and loose = total draw. The Unassigned appendix and route-less groups show the same three figures, or the figures are explicitly omitted there. Pick one and keep it consistent. Existing layout, row lists (starts/stops/paused) and per-route copy/delivery-point totals stay unchanged.
Planned
AI Studio - CMS website builder
🔍 Problem Statement As a Pelcro news client, I experience an AI Studio that only builds paywalls, which forces me to build and host my website elsewhere. 💡 User Story As a Pelcro news client, I want to build and host my website in the AI Studio by prompting, so that my site and paywall run on one platform. As Pelcro, I want get.pelcro.com built in the Studio, so that we validate the builder as its first client. 🎯 Definition of Done (DoD) ✔ Given the AI Studio, when a user starts a project, then “Website” is selectable alongside the paywall template. ✔ Given a website project, when a user selects or uploads a design template, then generated pages use its styles. ✔ Given a website project, when a user adds an API key in environment settings, then it is stored encrypted and available to the site. ✔ Given any prompt, when the Studio builds, then Pelcro’s built-in standards (content structure, PageSpeed, SEO) apply automatically. ✔ Given a website project, when a user imports from a public URL or a connected GitHub repo (supported stacks only), then the Studio rebuilds/loads the site and the normal prompt → preview → publish flow applies. get.pelcro.com is imported this way and published to Cloudflare as the first client. ✔ Given a published website (live on its Pelcro hostname), when a user connects their own domain, then the Studio: (1) verifies ownership with a non-disruptive TXT record and prepares TLS in advance, then (2) presents the single CNAME change as an explicit final “switch” step with a warning that it replaces whatever currently answers on that hostname, and (3) detects the switch and reports the site live. Nothing changes on the client’s domain until they consciously perform step 2. We never take over the client’s DNS. ✔ Given a website project, when a user creates, prompts, previews, or publishes, then each action runs through a documented, tested Pelcro API endpoint. Open Questions
Planned
Send email center emails from the client's support email instead of support@pelcro.com
🔍 Problem Statement As a client's subscriber, I receive Email Center notifications from support@pelcro.com instead of the client's support address, causing confusion and misdirected replies. 💡 User Story As a client admin, I want Email Center notifications sent from my brand's support email, so that subscribers recognize the sender and replies reach my support team. 🎯 Definition of Done (DoD) ✔ Given a site has a verified sender domain and support email, when an Email Center notification is sent, then the From address is the site's support email. ✔ Given a site's sender domain is not verified, when an Email Center notification is sent, then the Reply-To header is the site's support email. ✔ Given a client admin sets a sender email via [clarify endpoint], when the request succeeds, then the API returns the domain's SPF/DKIM verification status. ✔ This change will impact API and Email Center, specifically site sender settings and the Mandrill send pipeline. ✔ This solution will include the following limitations: custom From requires client DNS (SPF/DKIM) verification; unverified domains keep support@pelcro.com as From; Mailchimp and third-party ESP sends out of scope; per-template sender overrides [clarify].
In Planning
Allow renewal of expired subscriptions
🔍 Problem Statement As a business owner of a print publication with non-auto-renew subscribers, I can't renew a subscription once it has expired, so I have to create a new one, which skews renewal and churn metrics and print fulfillment lists. This affects every publisher using the invoice-pay or check-pay renewal model, which is standard for regional magazines, trade publications, newsletters and journals. 💡 User Story As a business owner, I want expired subscriptions to be renewable, so that they're recorded as renewals of the same subscription rather than new subscriptions. 🎯 Definition of Done (DoD) ✔ Admins (from the dashboard) and subscribers (from their account) can renew an expired subscription. ✔ The renewal continues the same subscription record and is reported as a renewal, not a new subscription. ✔ This change will impact the Dashboard, UI and API, specifically the renew subscription action.
Update Subscription Modal on Mobile Devices
Problem Statement: The current subscription modal on mobile devices does not align with the new design standards and needs to be updated to improve the mobile user experience. User Story: As a user accessing the website on a mobile device, I want the subscription modal to match the provided mockup so that I can easily view and interact with the subscription options. Definition of Done (DoD): Update the subscription modal on mobile devices to match the provided mockup. Ensure the modal is fully responsive across different mobile screen sizes. Ensure all buttons, fields, and subscription actions function correctly. Maintain the existing subscription functionality. A directly visible “Renouveler” action on eligible subscription cards, alongside “Gérer l’abonnement.” Distinct labels: “Expire le…” without automatic renewal and “Renouvellement automatique prévu le…” when enabled. “Modifier” updating only the selected subscription’s shipping address. The display of expired subscriptions in “Historique”, including access to renewal where eligible. Preservation of legacy Gift subscriptions’ recipient information and complete shipping addresses.
Individual Invoices
It would be helpful to be able to email an invoice to a customer on a one-off basis. I have the invoicing email disabled due to the way Pelcro structured my migrated accounts. However, there are many times I need to invoice for a subscription; for example, when I receive a subscription card it would be ideal to enter their subscription and email an invoice without having to toggle the universal invoice email on, then back off after I create the subscription and invoice the account.
In Progress
Legal Consent Checked by Default in Checkout
🔍 Problem Statement As a publisher, I experience friction at checkout when a customer must input their checkmark, which results in lost revenue. 💡 User Story As a publisher, I want the option for enableLegalConsent checkmark to be enabled by default, so that I can streamline my checkout process. 🎯 Definition of Done (DoD) A feature is done when: ✔ ️ Given the enableLegalConsent setting is used, when a second setting is introduced to toggle on the check by default, then the checkmark is enabled in the checkout flow. ✔ This change will impact [UI / API / SDK / Integration], specifically [describe endpoint, component, or area affected]. ✔ ️ This solution will include the following limitations [list constraints, edge cases, or scenarios not supported].
In Progress
AI usage dashboard: tokens and cost by service
🔍 Problem Statement As a business user, I have no visibility into the cost consumed by Pelcro's AI services, which prevents me from tracking and managing my AI spend. 💡 User Story As a business user, I want a dashboard showing token consumption and cost broken down by AI service, so that I can monitor and manage my AI usage. 🎯 Definition of Done (DoD) ✔ Given AI usage across services, when a business user opens the AI usage dashboard, then tokens consumed and associated cost are displayed per service (e.g. AI coding agent, AI customer service). ✔ This change will impact UI and API, specifically a new AI usage/metering endpoint and the dashboard. ✔ All AI projects use the centralized LangfuseTracer::trace() method, which detects and sets account_id, site_id and user_id as trace tags on every trace, at all times. ✔ An hourly cron job pulls the previous day's usage from Langfuse and saves only what is required (date, account, service, cost, input tokens, output tokens) in a local table. The dashboard reads from that table, not from Langfuse. ✔ The cron job stays within the Langfuse Metrics API rate limit (100 requests/hour on Core, shared org-wide) and handles 429 responses by waiting for Retry-After and retrying. ✔ This solution will include the following limitations: per-service aggregation only.
In Progress
Ticketing: automated CSAT survey emails on ticket solved
🔍 Problem Statement As a support manager, I can't collect satisfaction feedback on solved tickets, which leaves us with no CSAT data after leaving Zendesk. 💡 User Story As a support admin, I want to enable an automatic CSAT survey email in the Email Center, so that customers are asked for feedback after their ticket is solved. As a support manager, I want CSAT responses visible on the platform, so that I can review satisfaction per ticket and per agent without leaving Pelcro. 🎯 Definition of Done (DoD) ✔ Given CSAT is enabled in the Email Center, when a ticket has been Solved for 24 hours, then a survey email is sent to the ticket's customer. ✔ Given a Solved ticket, when it is reopened before the 24 hours elapse, then the scheduled survey is cancelled. ✔ Given a survey email, when the customer selects Good or Bad and optionally adds a comment, then the rating and comment are saved on the ticket. ✔ Given a ticket with a CSAT response, when an agent opens Ticket Details, then the rating, comment, and response date are displayed. ✔ Given the Tickets list, when an agent views or filters it, then a CSAT column shows each ticket's rating and the list can be filtered by rating. ✔ Given a ticket that already received a survey, when it is reopened and solved again, then no second survey is sent. ✔ Given a ticket with no customer email, or CSAT disabled in the Email Center, when the ticket is solved, then no survey is sent. ✔ This change will impact UI / API, specifically the Email Center CSAT template and toggle, the ticket status-change scheduler, a public survey-response endpoint, CSAT fields on the ticket resource, Ticket Details, and the Tickets list. ✔ This solution will include the following limitations: single survey template; binary Good/Bad rating; fixed 24-hour delay (not configurable); no aggregate CSAT dashboard or score trends in v1; survey link expiry.
In Progress
Ticketing: canned Tickets report under Reporting > Customer Service
🔍 Problem Statement As a support manager, I can't see a ticketing performance report in Pelcro like Zendesk's canned dashboards, which forces manual tracking of support performance. 💡 User Story As a support manager, I want a predefined Tickets report under Reporting, so that I can monitor ticket volume, satisfaction, and response times at a glance for a chosen timeframe. As a support manager, I want to see the CSAT responses customers submitted, so that I can understand the reasons behind the satisfaction score. As a support manager, I want to export the report, so that I can share it outside Pelcro. 🎯 Definition of Done (DoD) ✔ Given the Reporting page, when a manager opens it, then a new Customer Service section contains a canned Tickets report. ✔ Given the Tickets report, when it loads, then it displays fixed widgets for ticket volume, tickets per status, satisfaction score, CSAT responses, median first-reply time, and median resolution time. ✔ Given the Tickets report, when a manager selects a timeframe (last 7, 30, 90 days, or custom range), then all widgets reflect tickets created within that timeframe. ✔ Given a selected timeframe, when the report loads, then the volume widget shows the total number of tickets created in that timeframe. ✔ Given a selected timeframe, when the report loads, then the status widget shows the ticket count and percentage per status (Open, Pending, On-hold, Solved). ✔ Given CSAT responses in the timeframe, when the report loads, then the satisfaction widget shows the score as Good ÷ (Good + Bad), with Good and Bad counts. ✔ Given CSAT responses in the timeframe, when the report loads, then the CSAT responses widget lists each response with ticket ID, customer, assignee, rating, comment, and submission date, newest first. ✔ Given a CSAT response in the list, when a manager clicks its ticket ID, then the related ticket opens in Ticket Details. ✔ Given tickets in the timeframe, when the report loads, then it shows median first-reply time (created → first agent reply) and median resolution time (created → first Solved). ✔ Given the Tickets report, when a manager clicks Export, then a CSV with all widget figures and the CSAT responses list for the selected timeframe is downloaded. ✔ This change will impact UI / API, specifically a new Customer Service section on the Reporting page and a reporting endpoint returning the report figures and CSAT responses by timeframe.
In Progress
Surface Organization Field as Part of Checkout
🔍 Problem Statement As an Pelcro user, organizations cannot self identify as an organization in checkout, which results in unnecessary labor for me and confusion for my customers. 💡 User Story As a Pelcro user, I want the organization system to be self serve, so that my clients are able to correctly purchase and establish organizations for themselves. As a membership owner buying a multi-seat plan, I want to enter my organization name at checkout, so that my membership is tied to that organization. As a publisher admin, I want members added to a membership linked to the owner's organization, so that support can find any seat by organization. As a publisher admin, I want to require the organization field on membership plans, so that institutional purchases never land without one. 🎯 Definition of Done (DoD) A feature is done when: ✔ Given a membership plan with organization capture enabled, when a customer chooses a multi-user plan, then a mandatory free-text organization input is shown at checkout. ✔ Given a membership plan is purchased by an organization owner, then the membership is registered as an organization and the purchaser is the organization's owner. ✔ Given an organization name is submitted, when the membership subscription is created, then a new organization record is created and linked to the owner and membership. ✔ Given the purchaser already has an organization on their profile, when the membership is created, then their profile organization is kept (only filled in when empty), and the new organization is still linked to the membership with the purchaser as owner. ✔ Given a member accepts an invite to that membership, when their seat activates, then the member is linked to the membership's organization. ✔ Given the member already has an organization on their profile, when their seat activates, then their profile organization is kept (only filled in when empty), and they are still linked to the membership's organization. ✔ Given an organization owner or member is logged in, when the customer views their subscription, then their current organization is displayed and named as part of their subscription. ✔ Given the organization input is shown, when the customer types, then no existing organization names are suggested or shown. ✔ Given the organization input is shown, when the customer types, Pelcro does not check the organization name against existing organizations or indicate that a matching organization already exists. ✔ Given the organization input is shown, when the customer types in an organization that already exists, Pelcro creates a new separated organization. Organization names are not unique; the organization record is the identifier.
In Progress
Support Stripe Link payment method on the platform
Problem Statement Stripe's Link payment method syncs correctly to Pelcro's DB, but it is not displayed on the platform (e.g., on the customer's payment methods list). Link is also not listed as supported in our docs (https://docs.pelcro.com/docs/stripe#supported-payment-methods), so the behavior is currently unofficial and inconsistent: the data exists, but admins can't see or work with it. User Story As an admin/client, I want Link payment methods saved through Stripe to appear on the customer record, so that I can see how a customer is paying and allow customers who have Link as the only payment method to pay invoices correctly Definition of Done - A Link payment method synced from Stripe is displayed on the platform wherever other payment methods appear (customer payment methods, subscription details), with a clear label. - Link is usable as the payment source for subscription renewals and invoice payments, or its limitations are explicitly documented. - Existing Link payment methods already synced to the DB display correctly with no re-sync or backfill needed (or a backfill is provided if required).
In Progress
Support Avatax with Ecommerce
Problem Statement Pelcro currently does not support AvaTax tax calculation for e-commerce transactions. E-commerce SKUs may require different AvaTax tax codes, and taxes must also be handled correctly when orders are refunded or items are returned. User Story As a merchant using AvaTax, I want Pelcro to calculate taxes for e-commerce purchases based on each SKU’s AvaTax tax code so that the correct taxes are applied to purchases, refunds, and returns. Definition of Done Support AvaTax tax calculation for e-commerce transactions. Allow an AvaTax tax code to be configured per SKU. Send the applicable SKU tax code to AvaTax when calculating tax. Support different tax codes for different SKUs within the same order. Calculate and display the applicable tax correctly during e-commerce checkout. Ensure AvaTax-calculated taxes are reflected correctly on the resulting order/invoice. Support full and partial refunds with the corresponding tax adjustment. Support item returns and correctly reverse/adjust the associated tax. Refund and return tax behavior should be consistent with Pelcro's existing tax behavior. Existing e-commerce flows that do not use AvaTax remain unaffected.
In Planning
Send SMS and Facebook Messenger Messages via Automations
🔍 Problem Statement As a business user, I can only send campaigns to my segments over email, which limits reach to customers who don't engage by email. 💡 User Story As a business user, I want to send campaigns to my existing segments via SMS and Facebook Messenger, so that I can reach customers on their preferred channel. 🎯 Definition of Done (DoD) ✔ Given a segment in the automation tool, when a business user creates a campaign, then they can select email, SMS, or Facebook Messenger as the send channel and the message is delivered to that segment. ✔ This change will impact UI, API, and Integration, specifically the campaign/automation engine and the Integration Orchestrator (Twilio for SMS, Messenger Platform API for Facebook). ✔ This solution will include the following limitations: [clarify SMS provider]; sends to existing segments only; [clarify whether inbound replies are handled].
In Planning
Improve collaborator on-boarding experience
🔍 Problem Statement The current process of adding collaborators in Pelcro is time-consuming and inefficient, particularly for clients like Crain that manage multiple Pelcro accounts. When a new employee needs access to multiple accounts, admins must invite them separately to each account, resulting in approximately 15–30 invitation emails. The collaborator must then accept each invitation individually to activate their access. Additionally, if an invitation expires or is not accepted, admins must delete the pending collaborator and add them again to generate a new invitation. This creates unnecessary administrative effort and complicates collaborator onboarding. 💡 User Story As a Pelcro admin managing multiple accounts, I want to invite and manage collaborators more efficiently across all my Pelcro accounts, so that employees can access their assigned accounts without receiving multiple invitation emails or having to complete repetitive activation steps. 🎯 Definition of Done (DoD) 1. Send Invitation Emails Only to New Users Given a collaborator has never registered with Pelcro, when an admin adds them to an account, then send an invitation email to complete their initial account setup. Given a collaborator already has an active Pelcro login, when an admin adds them to another Pelcro account, then grant access without requiring another registration or invitation acceptance. Ensure existing collaborators can access newly assigned accounts using their current login credentials. 2. Allow Admins to Resend Invitations Given a collaborator has not completed their initial account setup, then provide a Resend Invitation option. Given an admin clicks Resend Invitation, then generate and send a new invitation email without requiring the collaborator to be deleted and re-added. Ensure the latest invitation link allows the collaborator to complete their registration successfully. 3. Simplify Multi-Account Collaborator Access Given a collaborator already has an active Pelcro account, when they are added to additional Pelcro accounts, then their access should not remain in a Pending status awaiting individual acceptance. Given a collaborator is assigned to multiple Pelcro accounts, then they should be able to access all authorized accounts using a single login. Eliminate the need for collaborators to accept a separate invitation for every additional account. 4. Centralized Collaborator Management (Nice to Have) Provide a centralized interface where authorized admins can view collaborators across multiple Pelcro accounts. Allow admins to add an existing collaborator to multiple accounts from one interface. Allow admins to remove collaborator access from selected accounts without switching between accounts. Display the accounts each collaborator has access to, along with their corresponding roles and permissions. Ensure all actions respect existing account-level permissions and access controls. Feedback: The process for adding a collaborator in Pelcro is clunky and error-prone, especially for Pelcro clients with multiple accounts. When we hire a new employee, we often end up adding them as a collaborator on all of our Pelcro accounts. This results in them receiving 15 to 30 invite emails, and they must click a link in each email to confirm each account. Should they fail to do so, we must delete their collaborator record in each account, and re-add them to generate a new invite email. Here is what I would suggest: Pelcro should only send an invite email to the user if they have not yet se