Create a Survey
I'm creating a survey for HR that will have 4 time periods (7 Day, 30 Day, 60 Day and 90 Day). My initial plan is to have the questions in a separate list and store the ratings for each of those questions with the Employee's Name in a separate list. I'm trying to figure out the best way to accomplish this.SharePoint and Power Apps: Managing Roles and Permissions
One of the key aspects of SharePoint security is managing permissions at the list or item level, which allows you to control who can view or edit the data. This granular control is essential for maintaining the integrity and confidentiality of sensitive information within your organization. By effectively managing permissions, you can ensure that only authorized personnel have access to specific data, thereby reducing the risk of unauthorized access. Whether you choose to restrict access to the entire list for simplicity or use item-level permissions for more advanced scenarios, SharePoint provides the tools you need to keep your data secure. Restrict Access to the Entire SharePoint List This happens in SharePoint itself, not Power Apps. You need to manage permissions at the list or item level: Go to your SharePoint site > Open the List. Click on the gear ⚙️ > List settings. Under Permissions and Management, click Permissions for this list. Stop inheriting permissions (click the ribbon command: Stop Inheriting Permissions). Remove default access groups (like "Members" or "Visitors"). Add a specific SharePoint group or individuals who should have full access —an admin or manager, not end users. End users will only interact with the list through Power Apps — they don’t need direct list access. Please keep in mind that if users need to edit entries, they must have access to the list. Without proper permissions, they won't be able to see or edit the list. The next user permissions option is ideal for users who need to edit their own entries. Use Item-Level Permissions in SharePoint This is only advisable if you can enforce it consistently: Go to List settings > Under Advanced settings. Scroll to Item-level Permissions. Choose: ✅ Read access: Only their own ✅ Create and Edit access: Only their own This works well only if users are submitting forms (e.g., time-off requests) that shouldn’t be visible to others. Prevent Users from Viewing or Editing Power App Code This is configured through Power Apps and Microsoft Admin Center. Limit Who Has Access to Edit the App In Power Apps Studio: Go to File > Share. Remove or do not add users as Co-owners. Instead, share as Users only — give them “Can use” permission. Use Environment Roles (Dataverse or Environment Scope) In the Power Platform Admin Center (https://admin.powerplatform.microsoft.com): Go to Environments > Click your environment > Security roles. Set roles so users: Are not Environment Admins or Makers. Only have User roles in production environments. Summary of What to Check: Task Where Goal Limit list access SharePoint List Settings Prevent users from directly viewing data Use item-level permissions SharePoint Advanced Settings Let users only see/edit their own submissions Limit app editing Power Apps Share Panel Ensure only owners can edit Secure environment roles Power Platform Admin Center Block access to Maker/Admin capabilities📈 How to create a Gantt Chart view in Microsoft or SharePoint Lists
NEW VIDEO N. 116 In this video tutorial, you'll learn how to change the view in a Microsoft or SharePoint List, setting up a Gantt Chart. We'll go through a modern technique that allows us to change the look and feel of a List. #Microsoft365 #Tutorial #GiulianoDeLuca #KnowledgeSharing #tips #tricks #tech #learning #MicrosoftLists #SharePoint #MicrosoftTeamsCreate an Internal Support Ticket Hub with Microsoft Lists, Forms & Power Automate
Setting Up the Support Ticket Portal First, we will set up the support ticket portal. This is where ticket requests will populate, be triaged, assigned and managed. It's a central location where the support team members can keep track of their tasks as well as keep the client informed through automated notifications upon status changes. Let's get started! 1. Create the Microsoft List: Navigate to Microsoft Lists from the Microsoft365.com App launcher in the upper left. Select the “+ New list” and choose the “Issue Tracker" template. Fill out the list information (name, description*, color*, icon*, and associate it with a team or save to your lists) and select create to make your form (*optional). In this case, associating the list with a team is required as it is needed for notification purposes later on in the tutorial. Review the list items from the template and customize the list to what your organization needs. Include columns that capture essential details such as issue description, priority level, assigned to, and status. Ensure the list is set up to store all necessary information for managing support tickets. There will be items you need captured from the person submitting the form as well as items to triage, assign, and track the status of the case. 2. Creating the Support Ticket Form In the list menu, select the "Forms" tab to create a new form. Customize the form by removing or unchecking questions that are designed for the support team, leaving only the questions needed from the person submitting the ticket. For example, you’d remove the Priority, Status and Assigned To fields from the form because those items are not determined by the submitter, but by the internal staff triaging the case. Ensure the form captures essential details such as the issue description, associated files, and contact information. 3. Enabling Notifications and Assigning Tickets In the form settings, select the toggle next to "Notify me" so that whenever a new item (support ticket) is submitted, you are immediately notified. This ensures that you don't miss an urgent request. Preview your form Check for changes or adjustments you’d like to make. If everything is good, congratulations! You’ve made your support ticket form! 4. The Workflow Process: Now that your form and list are created you can test out your new form and ticket portal. Grab the link to your new form by selecting the forms button again in the menu. Select the link sign to copy the link. Let's test things out. Fill out the form with information as if you are an employee submitting a ticket about an issue. Refresh and check your Microsoft List to make sure the form responses were automatically added. Triage the case. In the Microsoft List, double click on the form submission list item. Here, the support admin will triage the case by assigning it to a member of the support team, updating the status of the ticket to "In Progress" and assigning it a priority status. When a ticket is assigned, the assigned staff member receives a notification, ensuring they are aware of their new task. If they need to get in contact with the employee that submitted the case, they are able to come to the list item, and check for contact/email details in the email column. Team members can update the status of the ticket to "In Progress" when they start working on it and then to "Completed" once the issue is resolved. These status updates help track the progress of each ticket and ensure timely resolution. Congratulations! You have an internal support ticket portal and form. To further enhance the transparency and efficiency of your internal support ticket system, you can implement additional notifications to keep the requester informed about the status of their ticket. By setting up automated notifications in Power Automate for when a ticket is marked as "In Progress" and "Completed," you ensure that the requester is always aware of the current status of their issue. This not only improves communication but also boosts confidence in the support process, as employees feel assured that their concerns are being actively addressed and resolved. 5. Automating Notifications with Power Automate Create a Flow: From the Microsoft365.com app launcher, open Power Automate. Click "+ Create" and select "Automated Cloud Flow". Choose a flow name and set the trigger to "When an item or file is modified". Configure the Flow: On the canvas, select the trigger to enter the required data. The site address your Microsoft List is attached to and the list or library name. Next, we must add a trigger condition in order for the flow to only trigger when the status column has been changed. In the settings tab add the following trigger condition NOt(equals(triggerOutputs()?['body/Status'], triggerOutputs()?['body/PreviousStatus'])) Return to the canvas to create a new action. Select the + sign under your trigger. In the search menu, search for the condition action. For the value of the condition, we want to choose the Status Value from the dynamic field (the lightning bolt). We want to make sure the condition states “Status Value is equal to In progress”. (Capitalization matters here so make sure the capitalization of “In progress” matches the way it is spelled on your Microsoft List”. In the "True" column of your condition we will add a new action. Select “Send an email (V2) Inside of your action select, “Switch to Advanced Mode” to be able to enter dynamic fields or fields directly associated with your form submission. In the "To" field, select the lightning bolt for a dynamic entry. And select the “Issue logged by Email”. This will add the email address of the form sender to the “To” field and who the notifications will be sent to. In the Subject field type and appropriate title such as “Support Ticket Status Update”. In the Body field type a message to the requester. For example, "Hello, you are receiving this message to notify you that your support ticket for" (dynamically insert the name of the issue) “has been changed to “In Progress”. At this point, the flow now sends notifications for when the status column has been modified to “In Progress. Now, let's do the same and send a notification for when the status has been changed to “Completed”. In the False column, we are going to add another condition. The values for the condition will be the same except where it once said, “In Progress” it will say “Completed”. You want the statement to read “Status value is equal to Completed”. In the true column add the same action for sending an email and fill out the details accordingly. Save and test your flow. Test and Deploy: Test the flow to ensure it works as expected. Select Test and choose Manually. This specific flow is triggered when the status column has been modified to “In Progress” or “Completed”. Test both separately to make sure both works. You will see green check marks and receive a notification to the email you provided earlier when filling out the form with sample data. In this example, I tested the flow by updating the status to “In Progress” so in this case I have green check marks along the left side because that follows the first conditions. The green check marks will follow the right-side path if I choose to test the “Completed” status. Here is a copy of the email that was sent to the inbox. Once satisfied, deploy the flow to automate the notification process, enhancing communication and satisfaction. Conclusion By leveraging Microsoft Lists and Forms, you can create a robust internal support ticket system that streamlines the process of submitting, triaging, and resolving support requests. The integration with Power Automate further enhances this system by automating notifications, ensuring that all parties are kept informed throughout the process. This setup not only improves efficiency but also boosts employee satisfaction by providing a transparent and responsive support system.Building a Power App with SharePoint: A Series for Nonprofits
Introduction to the Series ➡️ Next: Building a Power App with SharePoint: An Overview Welcome to our step-by-step series on building a functional Power App connected to a SharePoint List — designed specifically with nonprofits in mind. Whether you're a nonprofit staff member looking to simplify your internal workflows or a tech-savvy volunteer eager to streamline operations, this series is for you. We’ll walk you through creating a simple yet powerful app that helps track records, use filters, and guide users through intuitive navigation — all using low-code Power Platform tools. This app can serve as a foundational template for many nonprofit scenarios like volunteer intake, service tracking, or resource request forms. Each blog post in this series will build on the last, using a SharePoint List as our backend and Power Apps as the frontend. 🎥 Take a Quick Look at the App Want a quick look at the final product before diving into the steps? Watch this short video overview of the custom Power App we built using SharePoint Lists and Power Apps. What We’ll Cover in This Series Here’s what you can expect across the series: Blog 1: Why Power Apps + SharePoint? A Nonprofit-Friendly Overview We’ll explain what SharePoint is, why it’s a powerful tool for storing data, and how it works seamlessly with Power Apps to create simple, low-code solutions for your organization. Blog 2: Building a Power App with SharePoint — Setting Up Your SharePoint List Before jumping into Power Apps, you’ll need a SharePoint List to hold your data. This post walks through how to create a list, configure the right columns, and prepare it to integrate with your app. Blog 3: Creating the Power App — Screens, Forms, and Filters In this final part, we’ll walk you through connecting your list to Power Apps, building the form screen, adding a view screen with filters, and setting up basic navigation to create a clean user experience. Who This Is For This guide is tailored for nonprofit professionals, accidental techies, or small teams trying to make the most of Microsoft 365 tools they already have. You don’t need a development background — just curiosity and a desire to build something helpful! Before You Begin To follow along, you’ll need: Access to Power Apps A SharePoint List you can connect to Basic familiarity with how Microsoft 365 works By the end of this series, you’ll have a working Power App that can be used as-is or adapted to suit your nonprofit’s needs. Let’s get started! 📚 Explore the Series Series Introduction An Overview of the SharePoint/PowerApps Combination Setting Up Your SharePoint List Building Your Power App
1000 Free Udemy Coupons on Microsoft Power Automate With AI Builder
<<BAKRI ID(Id-ul-Ad'ha) -- 1000 FREE UDEMY COUPONS ON RPA>> On the Occasion of BAKRI ID(Id-ul-Ad'ha), I am very happy to share 1000 Free udemy coupons on Microsoft Power Automate With AI Builder Title : Advanced RPA - Microsoft Power Automate With AI Builder https://www.udemy.com/course/microsoft-power-automate-with-ai-builder/?couponCode=LT-BAKRID <<Our other courses on Udemy and Udemy Business>> Title : PL-500 Microsoft Power Automate RPA Developer BootCamp Link: https://www.udemy.com/course/pl-500-microsoft-power-automate-rpa-developer-bootcamp/?referralCode=891491BAB7F20B865EE6 Title 1: Become RPA Master in MS Power Automate Desktop https://www.udemy.com/course/microsoft-power-automate-desktop-tutorials-for-beginners/?referralCode=03D49B549EE2193E79EE Title 2: RPA : Microsoft Power Automate Desktop - Zero to Expert : 2 https://www.udemy.com/course/microsoft-power-automate-desktop-course-zero-to-expert-2/?referralCode=783F39A1D0CDB4A70A7C Title 3: RPA:Microsoft Power Automate Desktop:Intelligent Automation https://www.udemy.com/course/power-automate-desktop-course-intelligent-automation/?referralCode=E8C51F3C27EA98FE100C Connect with me on LinkedIn : https://www.linkedin.com/in/ameer-basha-p-b44880262/ Youtube Channel : www.youtube.com/learningtechnologiesAnnouncing Agreements and Microsoft 365 Copilot Tuning integration
Intro In this AI era and fast-paced business environment, efficiency in reviewing and managing documents and agreements is crucial for achieving maximum productivity and compliance. Traditional methods of business document or agreement management involve cumbersome manual steps and result in lengthy processing times and error-prone agreement reviews. Infusing intelligence into these workflows can expedite processes from weeks to hours while achieving higher accuracy in reviews. With Agreements and Microsoft Copilot Tuning you can achieve just that. Today we are thrilled to announce the integration of Microsoft 365 Copilot Tuning within Agreements solution, empowering you to bring your own fine-tuned models in Agreements processes like AI-based Drafting, Review, Redlining, etc., and achieve next level productivity gain in the flow of work within Word and Teams experience. Read on to learn how these tools and this integration can enhance efficiency, accuracy, reduce paperwork, and ensure compliance with legal and regulatory requirements, making them essential for modern businesses. Agreements Agreements is an end-to-end solution that automates common workflows while enforcing the security and compliance promises of Microsoft 365. It is a comprehensive tool for automating high-value documents like NDAs, purchase agreements, HR offer letters, and engineering specifications. We released Agreements at Microsoft 365 Community Conference. We plan to make Agreements generally available this fall. You can import signed agreements into a central location, automatically extracting key information like counterparty and expiration date. This allows you to view all agreements with a specific counterpart and receive notifications when agreements are expiring, along with detailed reports. Figure: Importing signed agreements. To ensure thorough review of your agreements, you can establish key requirements, such as incorporating a privacy section. By utilizing AI to automatically examine your agreements, you can save time and efficiently identify instances where these requirements are not fulfilled. Coming Fall 2025, you can use Microsoft 365 Copilot Tuning to bring your own fine-tuned model into this review flow. Learn in the below section. Figure: AI assisted agreement review. Collaborating on agreements with external parties is a common scenario and we have it covered. With the Agreements solution, you can create secure Shared Channels for each client relationship. We currently support B2B customers and will soon add B2C user support. Agreements can be drafted, imported, revised with redlining, and electronically signed, either with SharePoint eSignature or third party eSign providers like Docusign and Adobe, all within a secure customer’s Microsoft 365 environment. Microsoft 365 Copilot Tuning It offers customers a new way to unlock the value of fine-tuning for organizations without the cost and complexity of other solutions. Now, makers can use low-code tooling in Microsoft Copilot Studio to take advantage of highly automated fine-tuning recipes that can use your enterprise data to build fine-tuned task-specific models. We announced Microsoft 365 Copilot Tuning at Build’25 Conference. Integration of Microsoft 365 Copilot Tuning within Agreements solution Coming soon, you'll be able to use fine-tuned task-specific models that you created with Microsoft 365 Copilot Tuning right within Agreements solution. Simply navigate to “Agreements” app in Teams, go to “Setup and access” tab, click “Custom model”. Then, pick from the catalog of fine-tuned models from your Microsoft 365 Copilot Tuning environment. It is that simple! You can associate models for specific AI tasks in the Agreements solution. For example, for AI-based Review task you can associate your “Legal FT model 2.0”. When the users go through that task, for example in Word while reviewing an Agreement, the associated fine-tuned model will automatically be used and offer more accurate results. Figure: Configuring fine-tuned models in Agreements app. Conclusion Together, Agreements and Microsoft 365 Copilot Tuning can help you securely organize and manage all your agreements, like purchase orders and engagement letters, within the security boundary of Microsoft 365. Interested in previewing this integration, sign-up in here: Agreements Sign-Up We encourage you to learn more about these powerful solutions: Agreements: Introduction to Agreements | Microsoft Learn Microsoft 365 Copilot Tuning: Introduction to Microsoft 365 Copilot Tuning SharePoint eSignature: Overview of SharePoint eSignature | Microsoft Learn If you’re at the Microsoft Build Conference this week, contact us at one of the activities below. Join us in our Breakout session 177: Fine-tune models for task-specific agents in Microsoft 365 Copilot, May 21, Wed 12:30 PM PST Visit us at the Microsoft booth: Microsoft SharePoint demo station We can’t wait to see what you build with these new tools. Sesha Mani Partner Group Product Manager Microsoft
