A practical guide to the myHood app for the person who manages a building.
This manual describes what the app actually offers (verified against the frontend and
backend code), and gives every screen, button and field name exactly as it appears in
the app in English.
- What is myHood
- Roles and permissions — the most important rule
- Installation and sign-in
- Your home screen (dashboard)
- Announcements
- Approving resident submissions
- Resident requests (handling reported issues)
- Community board
- My submissions
- Building members
- User accounts
- Buildings
- Messages
- Contacts
- Suggestions board
- Notifications
- Settings and your account
- Events (planned)
- What a manager can NOT do
- Common problems and solutions
- Quick reference: where to find things
1. What is myHood
myHood is a digital noticeboard, a pocket property manager and a neighbourhood group rolled into one. Instead of paper notices taped to doors, hunting for emergency numbers on gas cabinets and chaotic Facebook groups, everything important about your building lives in one place:
- Announcements — water shut-offs, power outages, meetings, repairs; delivered to
residents as an in-app item and as a push notification to their phone.
- Resident requests and complaints — a resident reports a problem, you track it, work on
it and close it out once it’s resolved.
- Community board — neighbours borrow tools, offer help, ask questions.
- Messages — direct and group conversations between building residents and you.
- Contacts — phone numbers and other contact details for building members in one place.
The app runs on the web (in a browser), on iOS, Android, and as desktop apps (Windows/macOS/Linux). All versions do the same things; some features (e.g. push notifications to a phone) naturally only work in the mobile app.
The app is bilingual (Slovak / English); you can change the language at any time in Settings or right on the sign-in screen. This manual describes the English interface.
2. Roles and permissions — the most important rule
myHood has three roles:
| Role (as shown in the app) | Who this is |
|---|---|
| „Resident“ | someone who lives in the building or owns an apartment there |
| „Manager“ | the person responsible for running the building — you |
| „Administrator“ | the operator of the whole system (not part of everyday building management) |
The most important rule: membership in a specific building decides, not just your role
Your rights in a building are not decided by your account having the „Manager“ role, but by whether you are a member record of that specific building with the role „Manager“ (or „Administrator“). This means:
- In buildings you manage, you have full manager rights (approvals, members, building
settings, …).
- **If your own account also lives in a different building as an ordinary resident, you are
genuinely just a resident there:** your announcements and posts there go into that building’s manager’s approval queue, you don’t see members‘ email addresses, and you have no „Add member“ button or „Building settings“ tile.
- A global administrator has rights in every building and additionally sees an extra
dashboard tile, „Admin“ (settings for the whole app). Everything else described in this manual applies equally to managers and administrators.
Overview: what you can do as a manager
| What | As manager in your own building | As manager in someone else’s building (where you just live) |
|---|---|---|
| Publish an announcement | immediately | goes into that building’s manager’s queue |
| Approve / reject resident submissions | ✅ | ❌ |
| Change a request’s status (triage) | ✅ | ❌ |
| Add members, see their emails | ✅ | ❌ |
| Edit / delete the building and its photos | ✅ | ❌ |
| Create a new account | ✅ (not with the administrator role) | ✅ (the same — does not depend on the building) |
| Write messages, comment, vote on the suggestions board | ✅ | ✅ |
3. Installation and sign-in
Launching the app
- Web: open the app’s address in your browser (e.g.
https://app.myhood.sk). - Mobile: install the myHood app from the app store (App Store / Google Play).
- Desktop: launch the installed application.
Sign-in screen
You’ll see the logo, the heading „Welcome back“ and the subtitle „Sign in to your building.“
- Enter your Email (the one your account was created with).
- Enter your Password (hidden by dots; a toggle next to it lets you reveal it
temporarily).
- Press „Sign in“.
If you’ve forgotten your password: below the form is a link „Forgot your password?“ — the screen it opens covers all three steps at once:
- Enter your email and press „Send email“ — you’ll receive an email with a one-time
code (the code is valid for 30 minutes and can be used only once). After sending, the app shows the „Check your email“ state with a „Resend“ button (locked for 30 seconds; the server allows at most 3 requests per 15 minutes per address — if you exceed the limit, the app tells you).
- Enter the code into the „Code from email“ field and set a new password with
confirmation.
- Press „Set new password“. On success, the app returns you to sign-in with the message
„Password changed — please sign in.“ and your email already filled in.
If you enter the wrong details, you’ll see „Incorrect email or password“ (the app deliberately does not say which one is wrong — for security reasons).
After signing in
The app remembers your session — after closing and reopening it, you won’t need to sign in again. The app routes you by role: residents get the resident home screen, you as manager (or administrator) get the manager dashboard (chapter 4). If your account belongs to multiple buildings and none is selected, you’ll see the prompt „No building selected“ with a „Choose a building“ button.
4. Your home screen (dashboard)
This is where everything starts — and where the app returns you on every launch.
Header
- A greeting based on the time of day („Good morning“ / „Good afternoon“ / „Good evening“)
with your name, and next to it the role badge „Manager“ (or „Administrator“).
- Building switcher — a button showing the current building’s name („Managing {name}“).
Tapping it opens the list of buildings you can see; picking another one reloads the whole dashboard for that building (overview, tiles, announcements). Most things in the app relate to this active building.
Building card
Name and address of the current building — a plain overview.
Overview row (three number tiles)
| Tile | What it counts |
|---|---|
| „Open requests“ | board posts in the „Open“ state — things still waiting to be handled |
| „Announcements“ | number of published announcements for the building |
| „Members“ | number of building members |
Quick action tiles
In a grid below the overview — in this order:
- „New announcement“ (Tell the building something) — creating an announcement (ch. 5).
Greyed out if you have no building selected or aren’t a member of it.
- „Review submissions“ (Approve what residents send in) — the approval queue (ch. 6).
If something is waiting in the queue, the tile carries a badge „{n} waiting for you“.
- „Resident requests“ (Review what was reported) — triage (ch. 7).
- „Members“ (Who lives here) — the building’s member list (ch. 10).
- „Messages“ (Chat with residents) — the inbox; unread messages show a badge
„{n} unread“.
- „New account“ (Onboard a resident) — creating a new user account (ch. 11).
- „Manage users“ (Browse and edit accounts) — the account list (ch. 11).
Note: browsing the full account list is an administrator feature — if you open it as a manager, you’ll see „You don’t have permission to browse user accounts.“ You still manage accounts from your own buildings via members (pencil icon on a row) and right after creating a new account.
- „Create building“ (Add a new building) — chapter 12.
- „Building settings“ (Details, photos and deleting) — **shown only if you are a
manager of this particular building** (or an administrator); leads to viewing, editing and deleting the building (ch. 12).
- „Suggestions board“ (Ideas to improve the app) — a global board for all roles (ch.
15); shown until an administrator turns it off.
- „Admin“ (App-wide settings) — administrators only; as a manager you won’t see
this tile.
Latest announcements
A section with the three most recent announcement cards and a „See all“ link to the full list (ch. 5). If the building has no announcements yet: „Nothing published yet — your first announcement will appear here — and on every resident’s home screen.“
Refreshing data
Pulling the screen down (pull-to-refresh) reloads everything — the overview, badges and members.
5. Announcements
Announcements are what the whole building sees: outages, repairs, meetings, general information.
List and detail
- The list (
/announcements) shows all published announcements for the active building;
new items are highlighted. Opening it clears the „new“ announcements badge.
- The detail view shows the full text, the category badge, an optional event date and
time (a row with a calendar icon), the author and the publish time.
- Attachments: images and files can be opened and saved („Save file“).
- Discussion: below the announcement is a „Discussion“ section — residents (and
you) can write comments.
- Your actions in the detail view (only as a manager of this building or an
administrator):
- „Add to announcement“ — add attachments even after publishing;
- pin / unpin to the top — a pinned announcement stays above the rest („Announcement
pinned to top“);
- delete — confirmed with a dialog „Delete announcement?“ („This announcement will be
permanently removed.“). The author can also delete their own announcement at any time.
Creating an announcement
Open the „New announcement“ tile (or the /announcements/new address). The form has these fields:
| Field | Required? | Note |
|---|---|---|
| Category | yes | one of five: „Water outage“, „Power outage“, „Meeting“, „Repair“, „General“ |
| Title | yes | up to 255 characters |
| Message | yes | multi-line text — what residents will see |
| When does it happen? (optional) | no | date and time picker; an announcement with a date also appears in the events calendar (ch. 18) |
| Attachments (optional) | no | images/files (up to 5 attachments per announcement, with size and type limits) |
As a manager you additionally see a „Pin to the top“ toggle above the form („Pinned announcements stay above the rest.“) and the button reads „Publish announcement“.
Key behaviour: the role that matters is your role in this building, not your account type in general.
- You are a manager of this building (or an administrator) → pressing „Publish
announcement“ puts it straight on the board and every resident gets a notification. Confirmation: „Announcement published“.
- You just live in this building → the screen instead says „Submit an announcement“, a
banner above the form reads „A manager checks announcements before the building sees them.“ and the button reads „Submit announcement“. After sending: „Sent to your manager for approval“ — the announcement waits in the queue (ch. 6) and you can edit it until it’s decided, in My submissions (ch. 9).
Known limitation: the text of a published announcement cannot currently be rewritten
in the app (the API has an edit endpoint, but the app doesn’t offer it yet) — please
re-read before publishing. You can already pin, add attachments and delete.
If you’re not a member of a building, you cannot publish an announcement to it at all („Announcements cannot be edited or deleted yet“ — sorry, the correct message here is: you can only post to a building you belong to).
6. Approving resident submissions
Everything residents submit (both announcements and community-board posts) that hasn’t been approved yet piles up in a queue. As the building’s manager, you’re the one who decides on them.
Open the „Review submissions“ tile (address /manage/moderation).
What you’ll see
A screen titled „Awaiting approval“ has two sections — „Announcements“ and „Community posts“ — sorted oldest first. Every card carries: a category badge, a title, a text excerpt, the submission time and the author’s name. (Older records that don’t carry a name are shown without that row.)
If the queue is empty: „Nothing to review“ — „Anything residents submit will land here first.“
Making a decision
Under each card you have two actions:
- „Approve“ — the submission goes straight to the public list (onto the board).
Confirmation: „Announcement published“ / „Post published“. The author gets a notification.
- „Reject“ — opens the dialog „Reject this submission?“ with the explanation „The
author is told. If you add a reason, they see that too.“ and a field „Reason (optional)“ (up to 1000 characters — e.g. „Please add which floor this is about.“). A red button confirms the rejection. The author sees the reason in My submissions and in the detail view as „Reason given“.
Each row is processed independently — deciding on one submission doesn’t freeze the rest of the queue. If someone else has already decided on the same submission (e.g. a second manager of the building), the app tells you with an error and the queue refreshes itself (the row disappears).
Why it’s worth watching
- The dashboard tile carries a badge „{n} waiting for you“ — the number in the queue.
- You receive push notifications „Announcements to review“ and „Posts to review“
(ch. 16) — these go only to the building’s managers, not to residents.
- An approved announcement with a date is also automatically added to the building’s events
calendar.
7. Resident requests (handling reported issues)
On the community board, residents report problems („Complaint“), make suggestions, ask questions. This is where you, as manager, track and change their resolution status.
Open the „Resident requests“ tile (address /manage/posts).
Filters
Two rows of chips:
- By status: „All“, „Open“, „In progress“, „Resolved“, „Rejected“.
- By category: „Complaint“, „Suggestion“, „Question“, „Neighbour help“.
The filters are mutually exclusive — you can pick either a status or a category (the API doesn’t support combining them); picking one clears the other.
Changing status
Under each card is a „Change status“ row with four chips — you can pick any target status (not just „one step forward“):
| Status | When to use it |
|---|---|
| „Open“ | reported, work hasn’t started yet (the default status of a new request) |
| „In progress“ | work is underway — e.g. a contractor has been called, parts ordered |
| „Resolved“ | done; the author gets a notification about the status change |
| „Rejected“ | it won’t be handled (e.g. it’s outside the building management’s scope) |
If a post no longer matches the current filter after a status change, you’ll see the message „Moved to ‚{status}‘ — no longer matches this filter.“ The „Open requests“ count on the dashboard recalculates itself.
If you open triage for a building you don’t manage, you’ll see „You are not a manager of this building.“
8. Community board
The community board (/posts) is the building’s public area: neighbours‘ posts as well as your own. Both roles use it the same way — for you it matters mainly in two respects: you as manager publish immediately (no queue) and you have broader delete rights.
List and detail
- The list shows posts approved for publication, newest first; new ones are highlighted. A
floating „New post“ button. Empty state: „The board is quiet“.
- The detail view shows the title, category, author and time, and below it a „Discussion“
section (comments). If you land on a post that isn’t public (e.g. via a link), you’ll see the badge „Awaiting approval“ / „Not published“ and possibly „Reason given“.
Creating a post
Fields: „What is it about?“ (category — „Complaint“, „Suggestion“, „Question“, „Neighbour help“), „Title“ (up to 255 characters) and „Details“. The intro line says: „Everyone in the building sees this, your manager included.“
- As manager of this building (or an administrator) → the button reads „Post it“ and the
confirmation is „Your post is up“ — it goes straight onto the board.
- If you just live in the building → the banner „A manager checks announcements/posts
before the building sees them…“ and the confirmation „Sent to your manager for approval“.
Known limitation: „While a submission is waiting for approval, you can edit it in *My
submissions*. Once it’s on the board, it can no longer be changed.“ (Only the author can
edit it — not even a manager rewrites someone else’s words.)
Deleting posts
- The author can delete their own post at any time.
- You as the building’s manager can delete any post in this building (confirmation:
„Delete post?“ — „This post will be permanently removed.“; its comments are removed along with it).
Two independent status axes
- Moderation (whether it’s public): „Awaiting approval“ → „Published“ or „Not
published“ — you decide this in the queue (ch. 6).
- Resolution status (triage): „Open“ → „In progress“ → „Resolved“ / „Rejected“ — you
change this in chapter 7.
9. My submissions
The „My submissions“ screen (/submissions) shows your own items in the active building that the building can’t see yet: „What you have sent in that the building cannot see yet. Approved submissions leave this list for the board.“
- A card with the status „Awaiting approval“ („A manager has to approve this before the
rest of the building sees it.“) or „Not published“ („A manager decided not to put this on the board.“) + when rejected, a row „Reason given“.
- For a submission that’s still waiting, you have an „Edit“ button — you can correct the
category, title and description („Save changes“ → „Your submission was updated“). The submission keeps its place in the queue — it’s a correction, not a new submission.
For you as a manager, this matters when your own account is merely a resident in a different building (ch. 2): there you’ll see your own submissions waiting for approval by another manager, and the reasons for any rejections. Empty state: „Nothing waiting“.
10. Building members
The member list (/members) is opened by both roles — for you it differs in three ways: you see email addresses, you have an „Add member“ button, and there’s a note under the list about a limitation.
The list
Every row carries: name, role in this building („Manager“ / „Resident“), apartment („Apt {n}“), entrance („Entrance: {e}“), bell („Bell {n}“) and, where applicable, the „Owner“ label. You additionally see every member’s email.
Adding members
The „Add member“ button opens the full „Add members“ screen:
- Search for a person by name or email (the search runs on the server; a query that’s
too short isn’t sent).
- People who are already members aren’t hidden — they’re marked „Already a member“ and
can’t be selected.
- Select multiple people at once. The role is set once for the whole selection (not
ten times over), while apartment number, entrance/street, bell number and ownership have their own fields per selected person („Apartment number for {name}“, etc. — all optional except the role).
- The „Add selected“ button submits everyone at once.
Result: if everything succeeded, you get a confirmation; if someone failed, a dialog titled „Result“ opens — „Added {ok} of {total}.“ with two lists: Added and Not added (with a reason: „Already a member of this building“, „This account no longer exists“, „That role cannot be assigned here“, „Selected more than once“).
Important pitfall: if you want to add someone who doesn’t have an account yet, you
must create it first (ch. 11) and after creation note down their numeric ID — the app
shows it to you with a copy button and a warning: „Note this ID down — you need it to add
this person to a building, and the API cannot look it up again.“ (Searching for existing
accounts while adding does work, but for brand-new people this is the procedure to follow.)
Editing a member
The pencil icon on a row opens editing — you can change only the entrance and bell („Entrance/street“, „Bell number“ → „Save“ → „Member updated.“). The role and apartment number cannot be changed once added — if that’s needed, the only path is to deactivate the account (ch. 11) and add the person again.
Limitation: „Members cannot be removed yet — the API has no delete endpoint.“
Taking someone off the list is only possible indirectly: by deactivating their account
(ch. 11) or by deleting the entire building (ch. 12).
Member profile
Tapping a row opens the profile: a header with role, apartment and ownership, the person’s list of contacts (ch. 14), and a „Send message“ action — a direct conversation (ch. 13).
11. User accounts
Accounts are what give people access to the app. As a manager you can create, edit and deactivate them — with the rules described below.
Creating a new account
The „New account“ tile (or /manage/users/new). Fields:
| Field | Required? | Note |
|---|---|---|
| Role | yes | chips „Administrator“, „Manager“, „Resident“ — as a manager you can only create a „Manager“ or a „Resident“; if you pick „Administrator“, the server rejects the request (only an administrator can grant that role) |
| First name, Last name | yes | |
| yes | must be valid and unique („That email already belongs to another account.“) | |
| Password | yes | at least 8 characters; a visibility toggle is available |
Button: „Create account“.
On success the app takes you to a summary with the new user’s name and — critically — a „User ID“ field (with a copy action) and a note to write it down: you’ll need this number if you add the person to a building. Buttons: „Create another“ / „Done“.
Browsing accounts („Manage users“)
The full list of accounts is an administrator feature. If you open the „Manage users“ tile as a manager, you’ll see „You don’t have permission to browse user accounts.“ — and that’s expected, not a bug. You still manage the accounts of people from your own buildings:
- via the pencil icon on a member’s row (ch. 10) — opens editing for that specific
account,
- via the summary right after creating a new account,
- and if you know the user’s ID, you can enter it directly in the address
(/manage/users/{id}).
Editing an account
The „Edit user“ screen has these fields: Role, First name, Last name, Email.
- Role: as a manager, your menu only offers „Manager“ and „Resident“ — a note under the
chips reads: „Only an admin can grant the admin role, so it is not offered here.“ If you’re editing an account that’s already an admin, this screen can neither promote nor demote it.
- Only what actually changed gets saved („Change something first“); another account’s email
is rejected („That email already belongs to another account.“); if the account doesn’t fall under your buildings → „You don’t have permission to edit this account.“ Success: „{name} updated“.
Changing a user’s password: the „Change password“ section opens the dialog „Change user password“ — you enter a new password with confirmation („Set a new password for {name}. The operator will not see it again after submitting.“). Beyond that, the person can change it themselves via password recovery.
„Entrance and bell“ section: if you opened editing via the pencil icon from the member list, it edits that specific membership directly; if the account belongs to more than one building, the app warns you: „This account belongs to more than one building — edit each one’s entrance and bell separately.“
Deactivating (deleting) an account
Inside account editing there’s a delete action with the confirmation: „Delete this user?“ — „Are you sure you want to delete {name}’s account? This action cannot be undone.“
Rules for who can deactivate whom:
- Never yourself.
- You as manager: only residents from your own building — not another manager, and
not an administrator. If the backend rejects the scope (e.g. the account belongs to a building you don’t manage), you get „You don’t have permission to delete this account.“
- (An administrator can deactivate anyone except themselves.)
What deactivation does: the account is disabled — the person can no longer sign in, old sessions stop working, and they’re removed from every building and contact list. Their posts, announcements and messages, however, remain (with the author attached) — this is a removal of access, not a deletion of history.
12. Buildings
Switching buildings
There’s no separate screen listing buildings — the only „menu“ of buildings is the switcher on the dashboard (ch. 4). It shows every building you can see, and picking one changes the active building.
Creating a new building
The „Create building“ tile (/buildings/new). Intro: „A new building becomes your active building as soon as it is created.“
| Field | Required? | Note |
|---|---|---|
| Building name | yes | 2–150 characters (example: „Green Court“) |
| Address | yes | 5–255 characters (example: „Main Street 123, Bratislava“) |
Note under the form: „Nothing here is permanent — the name and address can be changed afterwards, and the building can be deleted.“ On success: „Created {name}“ and the dashboard reloads to the new building. As its creator you automatically become a member with the „Manager“ role (and owner) — otherwise you’d be locked out of your own building.
Building settings
The „Building settings“ tile only appears on the dashboard if you’re a manager of this specific building (or an administrator). The screen has two parts:
- the „Edit building“ tile (Name, address and photos),
- a „Danger zone“ section with a red „Delete building“ button — „Deleting a building
cannot be undone. Everyone who lives here loses access to it.“
Editing a building
The fields are pre-filled: name, address, and two photo slots:
- „Profile photo“ — a square photo shown in building lists and in the switcher (up to 5
MB);
- „Cover photo“ — a wide banner behind the dashboard header (up to 5 MB).
Add a photo („Add photo“ / „Replace photo“ — source: Gallery, Camera or Files), a preview shows immediately, and „Remove“ deletes a published photo. Button: „Save changes“; if you change nothing → „Change the name, the address, or a photo first“. Everyone in the building sees the new details right away. If you’re not authorized (e.g. a manager from another building manually typed the address into the URL), the server responds and the app says: „Only a manager of this building can change its details.“
Deleting a building
Behind the „Danger zone“ door. Confirmation: „Delete building?“ — „Really delete {name}? This cannot be undone, and its announcements, posts and member list will no longer be reachable.“
Deletion is cascading: conversations with their messages, comments, posts, announcements with their attachments, calendar events and finally the building with its members are all removed. Success: „Deleted {name}“ — if it was the active building, the dashboard switches to another one.
13. Messages
Built-in chat between people from the same building. You have no special rights here as a manager — messaging works the same for every member (only building membership and participation in a conversation matter).
Conversation list (/messages)
Conversations for the active building, most recent activity first. A card carries the name of the other participant (for 1:1) or the group’s name, the time of the last activity, a preview of the last message and a „{n} unread“ badge. A floating „New conversation“ button; pull-to-refresh. If you stop being a member of the building, you’ll see: „You no longer have access to the messages for this building.“
New conversation
You pick a recipient from the building’s members (with search by name or email):
- 1 person → a direct conversation. If a chat with that person already exists, the app
simply takes you back into it (no duplicate is created).
- 2 or more people → a group conversation; requires a „Group name“ field.
Button: „Start conversation“ — on success, the new conversation opens directly.
Conversation detail
- Message history (newest at the bottom; older pages load as you scroll up).
- Composer: a „Write a message…“ field, a „Send“ button and an „Attach a file“
action (photos, camera or files; attached files can be removed).
- Message status: under your sent message you’ll see the progress „Sending“ →
„Sent“ → „Read“ (how others have read it).
- Realtime: an open conversation is watched live by the app — new messages arrive without
a refresh. If delivery were to fail, the app bar has an explicit „Refresh messages“ action.
- Search: the „Search messages“ action — the target message is highlighted and scrolled
into view.
Participants (group conversations only)
An app bar action opens the group’s member list:
- „Add participants“ — a picker from the building’s members; if every member is already
in the group, you’ll see „Everyone is already here“.
- Remove — confirmed with „Remove {name}?“. Any current participant can remove someone
(or an administrator); if not allowed, the server responds with an error.
Only the sender of a message can delete it (or an administrator) — merely being in the conversation isn’t enough.
14. Contacts
Contacts are a way to reach a person (type + value) that’s shared within the building. Two shapes of the same screen:
- „My contacts“ (
/contacts, linked from Settings) — your own list; everyone manages
their own.
- Member profile (from ch. 10) — the given person’s contacts.
Every row carries a type — „Phone“, „Email“, „Telegram“, „Other“ — and a value; the primary contact is marked with a „Primary“ badge. Adding a contact (dialog): pick a type, enter the „Details“ („Phone number, email, username…“) and toggle „Primary contact“; the „Save contact“ button → „Contact added“. Removal is confirmed („Delete contact?“).
Rules:
- Your own contacts you add, change and delete yourself.
- You as manager can add a new contact to another member’s list (e.g. add a phone number
you learned during a visit).
- You cannot edit or remove an existing contact belonging to someone else — only that
person can (or an administrator sharing a building with them). A read-only list for another member, without that permission, carries the note: „Only building managers can add or edit contact methods.“
The member profile also has a „Send message“ action (a direct conversation, ch. 13).
15. Suggestions board
A global board of ideas for improving the app (not the building) — open to every role, until an administrator turns it off. The dashboard has a „Suggestions board“ tile.
- List (
/feedback): cards with a title, an excerpt and a vote count („{n} votes“); an
app-bar toggle for sorting — „Sort by most voted“ / „Sort by newest“. A floating „Add suggestion“ button. Deletion is offered only to the author of their own suggestion (or an administrator).
- Creating one: fields „Title“ (up to 200 characters) and „Details (optional)“
(up to 4000); the „Save“ button → „Thanks! Your suggestion has been added.“
- Detail: the full text, a status badge, voting (votes can be withdrawn) and a
„Comments“ section.
- Statuses: „New“, „Planned“, „In progress“, „Done“, „Declined“.
Important for you: changing a suggestion’s status (or deleting someone else’s) can be done only by an administrator — as a building manager you vote and comment on the board just like residents do. A disabled board responds: „The suggestions board is off“.
16. Notifications
What you receive
| Type (as written in settings) | Who receives it | Where tapping it leads |
|---|---|---|
| „Announcements“ | building members | announcement detail |
| „Announcements to review“ | building managers only — a resident submitted an announcement | detail of the submitted (pending) announcement |
| „Posts to review“ | building managers only | home screen (a direct link is still being worked on) |
| „Messages“ | conversation participants | the conversation |
| „Community posts“, „Post status changes“, „Replies to discussions“ | building members | home screen |
For your work, the two review types are the most valuable — they alert you that something is waiting in the queue (ch. 6) before you even open the dashboard. These pushes go exclusively to members with the „Manager“ role in the given building; if you’re only a resident in a building, you won’t get its review notifications.
If tapping a notification can’t be handled (e.g. the item has since disappeared), the app does not crash — you stay where you were.
Notification settings (in Settings)
- The main „Push notifications“ toggle (if system permission was denied: „Notifications
are turned off“ + an „Open system settings“ button).
- „What to be notified about“ — toggles for the individual types from the table above.
- Reminder categories (9): „Maintenance“, „Meetings“, „Community“, „Deliveries“,
„Appointments“, „Amenity bookings“, „Utility notices“, „Personal“, „Other“.
- „Quiet hours“ („Silence notifications during a window each day.“) — „From“ / „To“
fields (crossing midnight is allowed); the times are in your own timezone.
- „Your devices“ — a list of devices you’re signed in on („Android device“, „iPhone“,
„Web browser“; the current one is marked „This device“) with a „Sign out“ action to remove a specific one (e.g. an old phone).
Saving: the „Save“ button → „Notification settings saved.“
17. Settings and your account
The „Settings“ screen (/settings) has these sections, in order:
Display
Text and icon size (a scale toggle) and appearance — light / dark / match device.
Language
„Choose your preferred language“ — Slovak or English. The translation is complete; the change applies immediately.
Notifications
See chapter 16.
Account
- Summary: „Signed in as {name}“ and role.
- Profile picture — „Add profile picture“ / „Change profile picture“ (photos, camera or
files; JPEG/PNG/WebP/GIF) and „Remove photo“ (reverts to showing initials).
- „Edit profile“ — fields First name, Last name, Email. Role and password
cannot be changed here (deliberately — only an administrator grants and changes the role). Success: „Profile updated“.
- „Change password“ — fields „Current password“, „New password“ (at least 8 characters),
„Confirm new password“. After a successful change, your session survives — old tokens are invalidated, a new one is stored, and you don’t need to sign in again.
- „My contacts“ — see ch. 14.
- „Sign out“ — with the confirmation „Sign out of myHood?“; it discards the whole app
state (queues, rosters, messages) and connections.
Deleting your account
Settings has a „Delete my account“ action — confirmation „Delete your account?“ with a „Yes, delete my account“ button. The account doesn’t disappear immediately: the app schedules the deletion and shows a snackbar with a date (a 3-day grace period), during which the request stays active and the app carries a warning banner. Within that window you can cancel it („Cancel deletion“). After the window elapses, the account is anonymised: the email and name are replaced, sign-in is locked forever, memberships, contacts and devices are removed — but your posts and messages remain in the building’s history, marked „Deleted user“.
About
Version; on the web, possibly a banner about a new version („A new version of myHood is available.“) with a „Reload“ button — after which the app is up to date again.
18. Events (planned)
The app’s backend can already work with a building’s calendar events (maintenance, meetings, outages — including recurring ones and RSVPs), but a user interface for events in the app doesn’t exist yet. A practical consequence today: an announcement you publish or approve with a date and time (ch. 5) is automatically recorded as a building event — so you’re already laying the groundwork for a future calendar without doing anything extra.
19. What a manager can NOT do
An overview of the boundaries, so you don’t bump into them by surprise (all enforced server-side):
- You cannot grant the „Administrator“ role — not when creating, not when editing an
account (it’s not offered to you).
- You cannot browse the full account list — „Manage users“ as a list is an administrator
privilege; you manage individual accounts via members and their IDs.
- You have no authority outside your own buildings — in a building where you just live,
you’re a resident: no triage, no approval queue, no adding members, no building settings (the server responds „You are not a manager of this building.“).
- You cannot deactivate another manager, an administrator, or yourself — only residents
from your own building.
- You cannot remove a building member — there’s no membership-delete feature; the only
path is deactivating the account (ch. 11) or deleting the whole building.
- You cannot change the role or apartment of an already-added member — only the
entrance and bell.
- You cannot edit another author’s post — not even as manager; you only change its
resolution status (triage) and may delete it.
- Public posts and approved announcements cannot be edited — after publishing you can
only delete them (and pin/unpin or add attachments to an announcement); a fix is only possible while the item is still awaiting approval.
- You have no special rights in Messages — you can’t read conversations you’re not part
of (this also applies to administrators), and only a current participant can remove someone.
- **You cannot change statuses or delete other people’s suggestions on the suggestions
board** — only vote and comment; statuses are managed by an administrator.
- You cannot toggle app-wide settings (e.g. turning off the suggestions board) — an
administrator privilege.
- You can only add to other members‘ contacts — you can’t change or remove another
user’s existing contact.
- You cannot change other users‘ notifications or devices — everyone manages their
own.
20. Common problems and solutions
| Symptom | Cause and solution |
|---|---|
| „Incorrect email or password“ | Check both; if it keeps failing, use „Forgot your password?“ (mind the limit of 3 requests / 15 min). |
| The app says it can’t reach the server | The backend is temporarily unavailable — try again later. On the web, a proxy sits in front of the app; if you launched the app differently (e.g. a local build), check the backend address configuration. |
| „You are not a manager of this building.“ | You’ve opened something in a building you don’t manage (ch. 2). Switch to a building you do manage. |
| „You don’t have permission to browse user accounts.“ | Normal — the account list is only visible to an administrator (ch. 11). |
| „Only a manager of this building can change its details.“ / „Only its manager can delete this building.“ | The action is outside the scope of your management of this building. |
| The approval queue is empty, but residents say they submitted something | A submission lands in the queue immediately; try pull-to-refresh. If it’s already been approved/rejected, you won’t find it in the queue — the author got a notification about the decision and can see the status in My submissions. |
| Changing status / approval fails with an error | Another manager of the building already decided on the same item. The queue refreshes itself. |
| Messages/comments don’t update on their own | The realtime channel is temporarily unavailable — use pull-to-refresh or the „Refresh messages“ action. |
| The badges (numbers) don’t match what you expect | Open that screen and pull down; the counts recalculate from the current data. |
| „That photo is too large“ / „That file type is not supported“ | Building photos are capped at 5 MB (JPEG/PNG/WebP/GIF); announcement attachments have their own limits — try a different format or a smaller file. |
| You’re signed out everywhere after changing your password | Changing it via Settings keeps your session alive; if the change happened another way (recovery via email), sign in again — old sessions are invalidated for security reasons. |
| You want to „fix“ a published announcement | The text can’t be rewritten in the app (ch. 5) — either delete it and republish, or add a correction as a comment underneath it. |
21. Quick reference: where to find things
| I want to… | Where to start |
|---|---|
| …tell the building something important | Dashboard → „New announcement“ |
| …approve / reject a resident’s submission | Dashboard → „Review submissions“ (or a push notification) |
| …respond to a reported issue and move its status along | Dashboard → „Resident requests“ |
| …write my own post on the board | Community board → „New post“ |
| …pin / add attachments to / delete an announcement | Announcement list → announcement detail |
| …see what I’ve submitted that’s still waiting | „My submissions“ |
| …add a resident to the building | Dashboard → „Members“ → „Add member“ |
| …create an account for someone who doesn’t have one yet | Dashboard → „New account“ → note the ID → add to the building |
| …edit / deactivate an account | Members → pencil icon on a row (or right after creating the account) |
| …fix a member’s entrance or bell | Members → pencil icon on a row |
| …rename the building / change its photos | Dashboard → „Building settings“ → „Edit building“ |
| delete an entire building (irreversible!) | Dashboard → „Building settings“ → „Danger zone“ |
| …connect a new building under my management | Dashboard → „Create building“ |
| …message a resident | Members → profile → „Send message“, or „Messages“ → „New conversation“ |
| …add a member’s phone number | Members → profile → add contact |
| …send a suggestion about the app | Dashboard → „Suggestions board“ |
| …set up notifications / quiet hours | „Settings“ → Notifications |
| …change my password or profile | „Settings“ → Account |
This manual is generated from the current state of the myHood app’s code (frontend + backend) and describes actual behaviour, including the limitations the app communicates directly to the user. If something in the app doesn’t look the way it’s described here, it’s likely a bug — please report it to the developer (e.g. via the suggestions board).