How do I join a CareLedger invitation?
Open the invitation link, install CareLedger if needed, authenticate, and review the care recipient and role before accepting.
Support
Help for the moments that get in the way.
Find clear next steps for invitations, accounts, reminders, shared care plans, privacy, and deleting your account.
Popular help
Start with the task you need to complete.
CareLedger support is organised around user actions, so you can find a recovery path without knowing the internal name of a feature. For account access, deletion, privacy or invitation help, email webalign.ug@gmail.com. Do not include passwords, one-time codes, reusable invitation links, or unnecessary care-recipient information.
The CareLedger approach
Good care coordination is not about adding more administration. It is about making the right context visible at the moment someone needs to act.
01
Start with the question you are trying to answer
Support works best when it starts with the moment that is blocked. Are you trying to join an invitation, find the care recipient you were added to, understand a reminder permission, or correct a care item? The links on this page are organised around those tasks rather than around internal product names. If you are helping someone else, describe the step you can see and the step you expected next when contacting support.
CareLedger is a shared care-coordination app, so a problem can involve both the device and the circle’s permissions. A person may have the app installed but still need to authenticate. A caregiver may be authenticated but not yet accepted into the selected recipient’s team. A reminder may be scheduled in the plan while the device permission remains denied. Separating those states helps avoid trying the wrong fix.
02
Joining an invitation
Open the invitation link on the phone you plan to use for CareLedger. The website acts as a safe handoff: it explains that someone invited you, gives you a path to the app if it is not installed, and keeps the invitation token opaque. When the app is available, it can receive the invitation context through the app link. You should then see the intended care recipient and the role you are being offered before you accept.
If you installed the app after opening the link and the handoff did not continue, return to the original link or use the recovery instructions shown by the invitation page. Do not post the token in a public message or send a screenshot that exposes it to people who were not invited. A token is intended to be short-lived access context, not a replacement for account authentication.
03
When an invitation does not work
First, check the simple causes. Make sure the link was copied completely and is not wrapped in punctuation. Open it on the same device you want to use for CareLedger. If the link opens a browser page, look for the invitation state and the button that continues to the app or store. If the app opens without the invitation, close it, reopen the original link, and confirm that the app is allowed to open supported links.
If the invite has expired, was revoked, or was sent to the wrong person, the owner of the care circle should send a fresh invitation. Support should not ask you to email private care details just to recreate a link. The safe recovery is a new opaque invitation tied to the correct recipient and role, followed by the normal authenticated join flow.
04
Account and sign-in help
Your personal account is separate from the care recipient and the care team. If you can sign in but cannot see a circle, the next question is whether the invitation was accepted and whether the membership is active. If you are creating a circle, onboarding may still need the recipient setup before the main app appears. If an authentication request is loading, preserve the intended invitation or onboarding action rather than starting over repeatedly.
Use the legal links near account creation and in Account settings if you want to understand privacy, terms, or deletion before continuing. A successful sign-in should return you to the flow you were trying to complete. If it does not, note the route you started from and the device platform when contacting support.
05
Reminder and notification help
CareLedger requests notification permission in context, after a reminder or schedule makes the permission relevant. The explanation tells you that notifications are used for upcoming care activities and that some Android devices may require battery settings to be adjusted. You can continue, or choose not now and use the app without immediately granting notifications.
If reminders do not arrive, check the app’s notification permission, the device’s Do Not Disturb settings, battery optimization, and whether the care item is still active. A permission denial should be treated as a recoverable state. The underlying schedule and care record should remain available even when device delivery is not.
06
Care plan and shared updates
If an item appears on the wrong person’s Today view, check the selected care recipient before editing it. If a task looks incomplete after someone says they finished it, open the item detail and review its current outcome and history. If an update does not appear immediately, check the connection and allow the app to synchronize before creating a duplicate record. Repeated taps can create confusion when the original write is still resolving.
A caregiver’s ability to edit or complete an item depends on their role and the permissions granted for that care recipient. Owners can manage the plan and team. Caregivers can view assigned information, complete permitted items, and add permitted updates. If someone needs more access, the owner should review the invitation or permissions rather than sharing another person’s account.
07
Privacy and sensitive information
CareLedger is designed for real care relationships, so it should be used with the same care you would apply to any shared record. Invite only people who should have access. Keep invitation links private. Use accurate but necessary information in notes, and avoid placing emergency instructions or sensitive details into a public support request. The website does not need to display the care recipient’s name in order to route an invitation.
The app’s privacy policy explains the categories of data, care-team sharing, authentication, notifications, storage, retention, deletion, and third-party providers that apply to the actual release. Product copy should not promise a privacy behaviour that the data model or vendors do not support. If something is unclear, ask support using a description of the behaviour rather than the care details themselves.
08
Support should protect the person at the centre
A support interaction should solve the technical problem without turning the care recipient into a case file. Start with the smallest description that explains the failure: the action, the screen, the device, and the message. Keep names, routines, medication details, and invitation tokens out unless they are genuinely necessary for a secure investigation.
That boundary is part of good support design. The people using CareLedger are often busy and may be asking for help while coordinating a real day. Clear recovery steps, honest limitations, and careful handling of shared information are more useful than a long checklist that asks them to disclose everything before anyone understands the issue.
09
When a problem is not yours to solve alone
Some issues belong to the circle owner rather than the caregiver who is seeing them. A pending invitation may need the owner to resend it. A missing permission may need the owner to review the role. A care-plan change may need agreement between the people responsible for the person receiving care. Support can explain the product state, but it should not quietly change another person’s access or decide what the circle’s care plan means.
Use the app’s roles and review flows for those decisions. That keeps the technical repair separate from the human responsibility that the shared plan represents.
10
A good support answer restores confidence
The best outcome of support is not only that a button works again. It is that the person understands what happened and knows how to continue safely. A clear explanation of an expired invitation, denied notification permission, or pending sync prevents the same uncertainty from returning at the next handoff.
If the product cannot complete an action, the error should say what the person can do next and preserve recoverable input. That standard matters especially in care coordination, where a confusing failure can lead someone to create duplicate work or make an assumption about what another caregiver has already done.
Common questions
Questions families ask about CareLedger.
Clear answers help a care circle decide whether the product fits the way they already share responsibility.
What should I do if an invite link fails?
Check that the link is complete, open it on the device you plan to use, and ask the inviter to send a fresh invitation if the original has expired.
Why did CareLedger ask for notifications?
Notifications are used for reminders you choose to enable. The app explains the request before opening the system permission dialog, and you can choose not now.
How do I delete my account?
Open Account settings in the app and use the account deletion entry. Review the confirmation carefully before completing the request.