Which Microsoft Graph permissions the Vitextra Employee Directory solution requests - Directory.Read.All, User.Read.All, Presence.Read.All, Calendars.Read and People.Read - what each one is used for, which web parts need it, what users see when it is not approved, and how to approve and check the permissions in the SharePoint admin center.
How the Vitextra Password Vault web part for SharePoint Online and Microsoft Teams protects personal credentials: Microsoft 365 sign-in and OneDrive access control, AES encryption of entry fields in the browser with a key derived from the PIN (PBKDF2), the locked vault, automatic lock, the five-attempt limit, what is and is not encrypted, the limits of a 4-digit PIN, and what Password Vault is designed for.
How the Vitextra Password Vault web part counts incorrect PIN attempts: the "Attempts left" message, the counter stored in the vault file across devices and sessions, its reset after a correct PIN, the Reset screen after five failed tries, what the reset erases, and why neither an administrator nor Vitextra can unlock the vault.
Why the Vitextra Password Vault web part requests the delegated Microsoft Graph permission Files.ReadWrite.AppFolder, what the permission allows and what it does not, how a Global Administrator approves it on the API access page of the SharePoint admin center, and what users see until it is approved.
Where the Vitextra Password Vault web part keeps your credentials: one encrypted file, vitextra-password-vault.json, in the app folder of your own OneDrive; one vault per user on all pages and in Teams; automatic creation; what happens when the file is deleted or moved; OneDrive requirements; how changes made on two devices are combined; and what to update after the upgrade to the new file format.
Answers to common privacy questions about the Vitextra Password Vault web part for SharePoint Online and Microsoft Teams: whether colleagues on the same page, page owners, site administrators, Microsoft 365 and OneDrive administrators, Teams channel members or Vitextra can see your entries, and what someone at your unlocked computer can see without the PIN.
Reference for SharePoint administrators and security reviewers: the Vitextra Discussions package requests no Microsoft Graph or other API permissions, needs no admin consent and no Microsoft Entra app registration, and works entirely through the SharePoint APIs (REST and CSOM) of SharePoint sites in the context of the signed-in user. What appears in the App Catalog and on the API access page, what the Teams app declares, what is sent to Vitextra, and where the e-mail permission of the optional Power Automate flow lives.
Reference for site owners and administrators on how the Vitextra Discussions web part maps SharePoint site permissions to what users can do: readers with Read, members with Add Items (Contribute / Edit) who post, reply, like, follow and report, and moderators with Manage Lists who approve, pin, feature, lock and delete. Covers guests, the default Members group, the visibility rule for pending posts and unique permissions on the Discussions lists.
Reference for administrators and security officers on the Vitextra Discussions web part for SharePoint Online and Microsoft Teams: the four lists and the document library the web part creates on the site, how the lists are recognised by column ids so they can be renamed, which columns hold topics, replies, mentions, likes and subscriptions, where attachments and inline images are stored, what is kept in the web part properties, the identity used for every call, what is sent to Vitextra and what happens to the data when the web part or the package is removed.
Reference for administrators and security officers on the Vitextra Questions and Answers web part: no API permissions, every call made as the signed-in user, the SharePoint list that holds questions, answers, attachments and comments, which SharePoint permission levels readers, askers and editors need, the limits of item-level permissions and publication control, what is not indexed by search, what the web part sends to Vitextra, third-party video embeds, retention and reporting with Excel and Power BI.
Reference on data handling in the Vitextra RSS Reader web part: why feeds are downloaded by the Vitextra feed service instead of the browser, exactly what the request contains, which permissions the solution needs (none), where the configuration is stored and who can read it, what is kept in the browser, how untrusted feed content is rendered safely, the hosts to allow on the network and recommendations for choosing feeds.
Reference for administrators, security officers and data protection teams: how Vitextra web parts for SharePoint Online and Microsoft Teams process data - in the browser, under the identity of the signed-in user - where each product stores its data inside your Microsoft 365 tenant, which technical data is sent to Vitextra services, which third-party hosts may be contacted, and what to allow on the network.