Clear answers before you begin
How building accounts, owner eligibility, decisions, contractors and data protection work.
Does Bendria work without a building association?
Yes. A building may be managed by a property manager, association or another lawful model. Organisations and their relationship to the building are stored separately.
Are records really stored in a database?
Yes. Accounts, buildings, memberships, initiatives, votes, tenders, projects, document metadata and audit history are stored in PostgreSQL and persist across sessions and deployments.
Is a Smart-ID sign-in already a qualified signature?
No. Everyday authentication and qualified signing of a specific ballot are separate actions. QES activates only with production provider access.
How is voting eligibility established?
Eligibility is linked to a specific premise, owner, ownership share, source and verification date. A specific register version is frozen before voting opens.
Does every decision use a 50% + 1 rule?
No. Quorum, voting base, weights, majority and abstention treatment depend on the decision category and the applicable legal procedure.
How are contractor bids submitted?
A contractor accepts a one-time invitation, links the legal entity and representative, then provides consistently structured prices, dates, warranty, declaration and documents. Every version is retained separately.
Who can see building information?
Only users with active membership in that building. Additional operations are role-limited and verified by the server on every request.
Which languages are supported?
bendria.lt serves Lithuanian and bendria.com serves English. Both domains use the same account and data.
Need a specific answer?
Tell us about your building, security or data-processing question.