# Editing or removing a user To change a user's role or remove them from your account, go to _Members_ and select _View and Edit _against the relevant person in the list: ![](https://images.prismic.io/bioscout/j4HiHVCBESi5-ZsQ_Screenshot2026-07-06154223.png?auto=format,compress) You can then manage their to access as follows: - _Edit Organisation Role _- this will change their overall access at the organisation level - _Remove Member _- this will remove the member from the organisation altogether - _Edit Site Role _- this will change their access at the individual site level - _Remove from Site _- this will remove the individual site access from the member --- # Understanding user roles Every BioScout user is assigned one of five roles within an organisation. Choose the role that matches what the person needs to do. #### **Organisation Admin** - Manage organisation settings, users and site access - Add and remove users; assign site-level roles - Full access to all site data and actions - _Best for: account owners and lead agronomists who oversee the whole account_ #### **Organisation User** - View spore graphs, weather data, spray logs and grower observations - Create and update spray logs and grower observations - Download CSV reports - Cannot change organisation or site settings - _Best for: field staff and agronomists who log activity in the field_ #### **Organisation Viewer** - View spore graphs and weather data only - Cannot download CSV reports or create/update any information - _Best for: stakeholders who need read-only visibility with no ability to make changes_ #### **Organisation Data Access** - View spore graphs and weather data - Download CSV reports for analysis - Cannot create or update spray logs, observations or site information - _Best for: data analysts or researchers who need export access but not operational control_ #### **Organisation Spore Analyst** - View spore graphs and pathology notes - Download CSV reports - Cannot view spray logs or grower observations - _Best for: sharing spore data with users from external organisations who should not have access to sensitive operational information_ **Note:** Users who work across multiple organisations (for example, an agronomist advising several growers) can switch between sites by using the _Filter Devices_ at the top of the _Disease Alerts _page. --- # Need help? If you run into any issues adding a user, contact the BioScout support team directly from the dashboard. Go to Contact Support at the bottom of the left-hand navigation, fill in the form, and we will get back to you. --- # Why am I seeing disease but no spores? It can be puzzling, and understandably concerning, to see disease symptoms in your crop while your BioScout graphs show no corresponding spore detections. Before assuming something is wrong with the system, it is worth knowing that there are several well-understood scientific and operational reasons this can happen. In most cases, the absence of a spore detection does not mean the platform is not working. It means the biology, environment, or conditions at the time did not produce a detectable airborne spore event. Below are the most common explanations. ## **1. The infection happened before spores were detected (latent period)** Fungal diseases don't show themselves straight away. There's always a **latent period**,  the time between when a spore lands on a plant and when visible symptoms appear. Depending on the pathogen and the conditions that follow, this gap can be anywhere from a few days to several weeks.  It is also worth knowing that even a very low level of spores can be enough to trigger an infection, depending on the crop growth stage and the environmental conditions at the time. If a small number of spores initiated the infection, the spore event that caused it may have gone undetected, both because it occurred well before symptoms appeared and because the spore concentrations involved were too low to register on the trap. By the time the disease becomes visible, the moment that set it all in motion may be long gone. ## **2. The fungus was not actively sporulating at the time of sampling** Many fungi produce and release spores only under specific environmental conditions, namely particular combinations of temperature, humidity, and light. If conditions at the time of sampling did not favour sporulation and spore release, there may be very few or no spores in the air, even though the disease is present and active in the crop.  Running all-day sampling can help reduce this risk. ## **3. Spore release occurred outside the sampling window** BioScout traps a sample for a defined period each day. If the main spore release event happened before or after that window, for example, early morning or late afternoon for some pathogens, it may not have been captured. Running all-day sampling can help reduce this risk. ## **4. The infection originated from a local or soilborne source, not airborne spores** Not all infections come from large airborne dispersal events. Some pathogens overwinter as dormant structures (such as oospores or sclerotia) in the soil or plant debris. These can cause primary infections in spring or early season without producing any or significant airborne spore cloud that a trap would detect. In these cases, disease can appear without any notable spore event preceding it. ## **5. The spore type responsible is not what our model is currently detecting** BioScout's detection models are built at the genus level and trained on specific spore morphologies. There are two scenarios where this can result in a missed detection: - **Different spore types within the same pathogen:** Some fungi produce more than one spore type (e.g., microconidia and macroconidia, ascospores and conidia). If our model was primarily trained on one type, it would not yet detect the other. This is something we actively work to address as we encounter new morphologies in the field. - **Morphological differences between species within the same genus.** Some fungal pathogens show distinct morphological differences across species that belong to the same genus. If our algorithm has been trained primarily on one species, it may not reliably recognise a closely related species whose spores look noticeably different. For example, _Peronospora destructor_ and _Peronospora belbahrii_ are both downy mildew pathogens within the same genus, but their spores differ enough that training on one doesn't guarantee detection of the other. The same applies to _Venturia pirina_ and _Venturia inaequalis_, which cause similar scab diseases on different hosts but have distinct ascospore morphologies. This applies to different species of Cercospora and Septoria as well. We actively work to expand our training data to cover these variations as we encounter them in the field.  ## **6. The spore count was below the detection threshold** Even if spores are present in the air, they may be at concentrations too low to trigger a positive detection. Very early in an epidemic, or when conditions are only marginally favourable for sporulation, spore levels can be real but below our system's detection threshold. ## **7. The unit was not positioned downwind of the infection source** Airborne spores travel with the wind. If the BioScout unit is not located downwind of the area where infection and sporulation are occurring, it may not sample those spores even if they are present in the field. Positioning and prevailing wind direction are important factors in interpreting spore data. ## **8. The disease may be caused by a different pathogen or an environmental condition** In some cases, similar symptoms in plants can be caused by different pathogens, or sometimes due to abiotic disorders (non-infectious) such as chemical burns, nutrient deficiencies and water/sun stress, making diagnosis challenging. Because of this, it is important to consider in some cases it is likely that the symptoms being observed may not be caused by the pathogen initially suspected. If a different fungal genus, or even a bacterial or viral pathogen, is responsible, the spores expected to be associated with the disease may not be present.  ## **9. The tape scan may be obscured by dust or debris** If the BioScout tape inside the unit becomes heavily contaminated with dust or fine particulates, it can obscure spores, particularly those that are small or colourless. In these conditions, spores may be physically present on the tape but invisible to the detection algorithm. Keeping the unit clean and checking tape condition regularly helps avoid this. ## **10. The unit may be experiencing a hardware issue** In some cases, the unit itself may be partially blocked, not drawing air correctly, or experiencing another hardware issue. If you suspect this is the case, please contact the BioScout support team so we can investigate. ## **In summary** The absence of detected spores does not necessarily mean the BioScout system was not working. It is more likely to reflect the natural biology of the pathogen, including its latent period, environmentally driven sporulation patterns, and the possibility that the infection originated from a source our trap was not positioned to sample, or from a spore type our model is still being trained to detect. If you are seeing disease without any preceding spore signal and cannot identify a likely explanation from the list above, please reach out to us directly. We want to understand what is happening and help you get the most out of your system. --- # How to add a user to BioScout You can invite coworkers, agronomists and advisors to access your BioScout dashboard directly from the _Members _section. Each person you add receives their own log-in and is assigned a role that controls what they can see and do. ### Before you start You need to be an _Organisation Admin_ to invite new users. If you do not have admin access, ask your _Organisation Admin_ to send the invite on your behalf. Note: Not sure who your Organisation Admin is? Contact support@bioscout.com.au and we can confirm this for you. ### Step-by-step: inviting a new user **Step 1: ** Open _Members _in the left-hand navigation menu and select _Invite Member. _ ![](https://images.prismic.io/bioscout/mFnWfpJoxtDJJJjY_Screenshot2026-06-30115151.png?auto=format,compress) **Step 2: ** Enter the user's email and select the appropriate _Organisation Role _(click on _How Roles Work_ for further details). ![](https://images.prismic.io/bioscout/JfpGpZmBeaVJdlJQ_Screenshot2026-07-06151611.png?auto=format,compress) **Step 3: ** If you manage more than one organisation, use the organisation selector at the top of the page to choose the account you want to add the user to **Step 4: ** Select which site this user can access by checking the boxes against each site **Step 5: ** Select _Send Invitation _ **Step 6: ** The new user will receive an email from BioScout with a link to set up their account. Once they accept, they appear in your team list with the assigned role **Tip:** Invited users must accept through the email link to activate their account. If they have not received the email, ask them to check their spam folder or click ‘Resend’ under the Actions column in the _Invitations _tab.