Portal / Dashboard
Each user role has a dedicated dashboard providing them with the tools they need.
-
Client Dashboard:
- Request new services for specific locations.
- View upcoming and past appointments.
- Manage multiple properties ("Homes") and specific areas within them ("Spaces").
- View and manage a digital inventory of their plants.
- Access the Smart Garden Assistant for AI-powered insights.
-
Gardener Dashboard:
- View a list of assigned clients and their upcoming jobs.
- Track earnings, including gross income and net pay after franchise fees.
- Manage their work availability and schedule.
-
Admin Dashboard:
- A comprehensive overview of all business metrics.
- Leads Management: View and manage incoming inquiries from contact and quote forms.
- Client Management: See a full list of all users, assign gardeners to clients, and view detailed client profiles.
- Financial Oversight: Track total platform revenue and view all invoices.
- Status & Details
- Research
- User Focused
- Features & Functions
- Data
Status
| Owner | Lead | Doc Status | Product Status | Last Update | Version | Release | Phase |
|---|---|---|---|---|---|---|---|
| Mendy | Esti | In Progress | Up Next | 04.03.2024 | 0.01 | Internal | Alpha |
These details are only updated with each release, for more acurate updates and keeping track of progress, see the task in GitHub.
Description
The account serves as a source of ownership and truth, here the client can keep data about thier users, BackBone will also have its users to ensure information provided to clients are acurate. Users can keep all thier details in order to enjoy all the features our APIs and what the client offers them.
Reminders
Links & Resources
Research
the research listed here is spesifict to the User (Account) feature, for research related to the general BackBone development see the Research document.
In the course of our research, we discovered many tools that will help us achieve the project goal. This document contains the research that was done for both [Dance] and [Dance Console], thus it is the [Dance Project] Research. To read about the conclusions drawn from the research one should read the complete Dance Project Description and its accompanying documents.
Technical
Question - How do we get data from arenas to form the arena layout and map the devices?
Answer - In our research we found many [API]s that give us much information but they are all very limited and expensive.
We
Conclusion - How do we get data from arenas to form the arena layout and map the devices?
Sources
- [test]
Business
User Stories
Persona One
Update Coming Soon
As a busy user I don’t want to watch but rather listen to a podcast, however, when I hear a voice I don’t recognize, I want to take a glance at my phone to see a name and/or photo of who is talking or maybe ask the built-in “AI/assistant”.
Flows
Personas
Features
Below is a list of features that will be utilized in order to deliver the best account features and functionalities. The details bellow are not comprehensive feature details but rather, describe how the features will be utilized within the account, for further details, please see the individual feature documentation.
-
Authentication
Not all accounts will requier auth, indevidual accounts will need to authenticate however the client can indecate what account types do not need auth and will instead be accessed though indevidual accounts. If auth is not reqried than access is reqied and vs.
-
Access
If the account type is not "indiviual" the account will not have an auth method and thefore will reqesre access. This will be a sub-collection within the account document that will hold the account, group, etc IDs of anyone who has access to this account.
-
[Account recovery]
-
[Flags]
if an account seems suspisus it should be flaged so that any channel, content, comments or otherwise can be monitored
-
Anonomus User (Account) 2.0
On the document we want to keep all the important data, the first fetch and fast to access, all secondary data should be stored on a subcollection and fetch sepratly (if this is cost sfective)
User Accounts should be a top level collection, each account will generate a new document within the "Accounts" collection.
Account
- Account
- - Acount 1
- - - type (offer a fea default options that the client can configure as well as custome options or offer numbered types and allow te client to give each type a title, this will enable the client to offer difrent feature or access levels based on account types)
- - - email
- - - number
- - - legal name (if connected wit a / our identity API this will allow for name/identity varification, useful for saftly and fintech and fraud protection)
- - - age (also opcinaly connect with identity api for varification)
- - - dob (also opcinaly connect with identity api for varification)
- - - varified (true, false)
- - - created (date)
- - - timezone
- - - langages
- - - contact detail
Names
- names
- - name 1
- - - type (legal, nicname, madename, etc)
- - - name
- - - laguadge
- - - created (date)
- - - varified (true, false)
- - - varified source (api id)
Identification
- id
- - id 1
- - - type (licence, passport, health card, etc)
- - - issuer (US gov)
- - - id number
- - - status: verified
- - - issued (date)
- - - experation (date)
- - - Verify provider: (api id)
- - - Verify date: log id
- - - image
- - - id_proof`
Sessions
- Sessions
- - Section #1
- - - auth type (OTP, Google, Apple, Normal)
- - - device_type (Android, IOS, Web)
- - - device_token
- - - location
- - - activated (date)
- - - status (active, inactive)
- - - inactive (date)
Locations
Preferences
- prefrences
- - communication
- - - method (push, email, text)
- - - default (true, false)
- - - allow (true, false)
- - - block (true, false)
- - - level (all, update, security, system)
- - - channels (id, id, id)
- - privacy
- - - allow (true, false)
- - - block (true, false)
- - - allow user data collection (true, false)
- - - allow user data share (true, false)
- - - allow user data anonymize (true, false)
- - - allow user data deletion (true, false)