Urbira

A guide to your Urbira community workspace

Learn to connect with your community in Urbira, participate in polls, review documents with AI, create invoices, and follow everyday work.

Urbira Product TeamUpdated Boards · Managers · Homeowners

Start with your community

Urbira brings residents, boards, and administrators together around the same community. Use the wall to share updates and follow conversations, then open the related financial, maintenance, or document record when a task needs more detail. What you can see and change depends on your role and the community’s settings.

The web workspace supports administration and detailed reviews. The mobile app is available for Android on Google Play and for iOS on the App Store for community updates and everyday participation. The available actions can differ by installed app update, device, role, and community settings. Use the task guides below to check where to complete each workflow.

Find a task walkthrough

Start with account setup and recovery, joining your community, or mobile and web availability. Administrators can follow access-request review and link sharing.

For communication, use private Messages and notification settings and phone alerts. Messages has an account inbox across communities; each thread keeps its original community and sending permissions.

For daily work, follow projects on mobile, files and previews, electronic contracts, or finding community information.

For financial work, use invoices, bills, and payments, credit notes and corrections, and document-analysis history. Read usage-credit funding before a metered task; a participant’s role affects whose balance funds it. Deletion, archive, and retained history explains how visibility changes differ from reversing financial activity.

Choose the community and find what needs attention

After signing in, confirm the selected community before opening or changing a record. People, units, financial information, work orders, documents, permissions, and activity remain tied to that community. If your account has access to more than one, switch deliberately rather than assuming the last view belongs to the work in front of you.

Use the dashboard and relevant lists as starting points. Look for an open item, upcoming date, recent update, or record related to your responsibility. Then open the underlying item. A summary helps you notice work; the detailed record provides the context needed to continue it.

Before acting, confirm three things: what happened, who currently owns the next step, and what your role permits you to do. If information appears incomplete, add context or ask the responsible person instead of creating a disconnected duplicate.

Connect through the community wall

Start with recent posts to understand what is happening. Read the conversation before replying, add useful context in a comment, and use a reaction to acknowledge an update. When you share a photo or document, explain what it shows and why it matters. Keep private account details and sensitive documents out of a general community conversation.

Publish a new post for a new topic. Continue an existing conversation when you are responding to that topic, so neighbors can follow the exchange in one place. On the web, the wall index helps you find a recent post without scrolling through the entire feed.

A community conversation can clarify a concern, but it does not replace a formal maintenance request, financial review, or official notice when your community requires one. Connect the conversation to the appropriate next step.

Participate in a poll and confirm your vote

Read the question, available choices, voting period, and eligibility before selecting an answer. Some polls are limited to unit owners. A poll may also be scheduled, closed, canceled, or not yet published; its message explains why voting is unavailable.

Selecting an option is not the same as submitting a vote. Submit your choice and look for the confirmation that your vote was recorded. If saving fails, your selection is kept so you can try again. Where voting remains open and changes are allowed, save your revised choice and confirm it again.

Use the results view when it is available. If results cannot be loaded, try again later rather than assuming there were no votes. Participation in a poll does not by itself replace a legally required meeting, notice, or approval procedure.

Follow a maintenance report from intake to follow-up

Start with a clear description of the condition and location. Add when it was observed, useful photos or documents, access information, and the person reporting it. Confirm whether the request belongs in the selected community and whether responsibility still needs review.

Use the work order record to assign or identify responsibility, track status, connect a service provider when appropriate, preserve supporting files, and record related costs or updates. Permissions and community procedures determine who may make each change. A work order organizes the facts; it does not decide legal responsibility or authorize work by itself.

As the matter progresses, update the existing record. Note material vendor or resident communication, changed dates, approvals, completed work, and remaining questions. At follow-up, another authorized person should be able to see the reported condition, action taken, current status, and next step without reconstructing the history from email.

If the work involves an owner modification or formal approval, use the community’s process and the architectural request guide to organize the submission.

Review a financial or document item with the right access

Begin with the record that needs a decision or follow-up: an invoice, bill, payment, account item, report, document, meeting item, or community update. Check the selected community, source document, date, status, and related activity. Do not assume that seeing a record gives authority to approve or change it.

For a financial item, connect the supporting document and confirm who reviews, approves, pays, or receives the report under the community’s procedures. For a document or community item, identify the current version, intended audience, required response, and any date that controls the next action.

Use communication, calendar, poll, board, people, and document tools when they support the task. Keep the result with the record: what was reviewed, what decision or response occurred, who is responsible now, and when it will be checked again. Sensitive information should remain limited to roles with appropriate access.

Turn a document into a reviewed invoice

For an authorized financial workflow, upload the supporting document and use AI-assisted extraction to prepare the information for review. Compare the recipient, dates, descriptions, amounts, and total with the original. Correct anything incomplete or inaccurate before creating the invoice.

If the document uses another currency, review the currency and decide whether to apply conversion when it is available. Check the exchange rate and the amount that will be recorded. Where applicable, review the unit’s printed share or configured allocation percentage, any explicitly confirmed document credit or debt, and justified rounding adjustments. A prior amount on the source is a document adjustment, not an automatic statement balance. See the guides to currency conversion and shared-cost allocation for examples.

The review is your decision point. AI helps read the document; it does not approve the expense or determine who should pay. For a complete walkthrough, use the document-to-invoice guide.

Get help without losing your place

Use the help icon in the web workspace when you need guidance on Urbira. Describe what you are trying to do and where you are stuck. You can return to saved support conversations instead of starting over each time.

If a message is waiting to be sent, you can review, edit, or remove it from the queue. Avoid sending the same question repeatedly while a reply is pending. Product help does not replace your community’s contact for account disputes or local emergency services for urgent safety concerns.

Preserve context when work changes hands

A useful handoff does more than change an assignee. Review the status, next action, date, responsible role, supporting files, and unresolved questions with the incoming person. Add any material conversation or approval that exists outside the workspace, subject to the community’s privacy and record practices.

Use activity history to understand the sequence, but summarize the current state so the next person does not have to interpret every event. If a board is organizing recurring responsibilities and backups, the self-managed board operations guide provides a broader handoff checklist.

When a person’s role ends, authorized administrators should review permissions and preserve required records. Community continuity depends on the shared record, not one person’s inbox or memory.

Understand who manages the subscription

The account responsible for your community manages its Urbira subscription. Invited homeowners and residents use that coverage without buying separate plans. Read the subscriptions guide to understand who gets charged, how unit limits and credits work, and what to check before renewal or an administrator handoff.

Complete an end-to-end trial check

New accounts receive a 30-day trial. Use a test community or suitable sample information before recording live activity, then complete this check:

  1. Confirm the selected community and your role.
  2. Open a real type of work, such as a maintenance request or document review.
  3. Add the starting facts and one supporting file.
  4. Assign or identify the next responsible person.
  5. Change the status or record the review allowed by your permissions.
  6. Add a follow-up update and next date.
  7. Ask another authorized user to find the item and explain what happens next.

Also try a wall conversation and an eligible poll, confirming that the reply or vote appears as expected. If you manage finances, review a sample document and create an invoice only after checking the details. Ask an Android or iOS user to complete the actions available to their role. Note permission gaps, unclear ownership, and any step that still depends on a separate message. Evaluate the actions you can use today; do not assume an untested requirement or a planned capability is already covered.

From context to action

A connected community starts with a shared space.

See how Urbira connects conversations, records, and responsibilities to keep community work moving forward.

Explore features