Why SharePoint is Good for the Bottom Line

The following are some key aspects of why SharePoint is good for the bottom line:

Slash product costs - the M365 ecosystem which includes SharePoint, Power Platform, Power Apps, Power BI gives one the needed tools and therefore eliminates unnecessary spending on applications and tools. 

Optimize licenses - M365 which SharePoint is a part of, let's one identify where they can scale back without sacrificing productivity. 

Create & monitor tickets - SharePoint allows several out of the box templates to streamline a ticket management processes effortlessly. 

Trigger workflows from within SharePoint sites - Allows the unleashing of integrated automation via Power Automate.  

Delegate key tasks - SharePoint sites can use powerful list templates to empower a team with streamlined task delegation via simple workflows.

SharePoint - Data loss prevention (DLP)

The following is a SharePoint dictionary word of the day:

Data loss prevention (DLP)

Allows way to monitor and respond to sensitive information within an organization through content analysis. DLP can flag certain messages and alert users when they try to send or post personally identifiable information (PII).

SharePoint - Data Connection

The following is a SharePoint dictionary word of the day:

Data connection

Link between an application and a data source. Data connections are used to query and submit data. They are utilized with an external data source, such as a database, Web service, SharePoint list, or XML file, etc.

5 Core Success Measurements for SharePoint

The following are the five-core success measurement for any SharePoint project:

1) On-time delivery - the SharePoint functionality was built and deployed on time.

2) Product quality - the SharePoint functionality has minimum bugs and errors.

3) Customer user/satisfaction - the SharePoint functionality is well received by the end users.

4) Business value - the SharePoint functionality provides high business value and cost savings.

5) Product scope (features and requirements) - the SharePoint aspects deployed are part of an on-going cycle of useful features based on needed requirements.

4 High-Level Planning Process SharePoint Aspects

The following are four high-level aspects to utilize as part of the planning process in SharePoint:

1) Have a detailed discovery process to find out what the end user wants

2) Have a segmentation funnel to give the end user what they want

3) Have the ability to watch traffic to see what is being utilized to allow for a better launch, grow, & scale of the created functionality

4) Have follow-up meeting to discuss any concerns to improve the process being built

SharePoint - Custom

The following is a SharePoint dictionary word of the day related to custom:

Custom action

Extension to user interface – such as a command on the ribbon or list item menu.

Custom master page

Used by publishing pages on a publishing site, represented by the token ~masterurl/custom.master.

Customized web page

Web page that is stored within a content database.

SharePoint - Crawl

The following are SharePoint dictionary words of the day related to crawl:

Crawl

The process of traversing a URL to acquire items for a search catalog.

Crawl log

Provides information about the results of crawling a URL. The information includes if the crawl was successful, the content source that the display URL belongs, and the level, message, time, and identifier of any errors that happen.

Crawl queue

A structure that stores the list of items to crawl next.

Crawl rule

Preferences that apply to a specific URL or range of URLs. A crawl rule can be utilized to include or exclude items in a crawl. Additionally, the rule can specify the content access account to use when crawling a URL or range of URLs.

Crawl status

The state of the crawl operation (example In-Progress, Suspended, etc.).

Crawl type

Specifies whether to evaluate all of the users and member groups in the directory service that is crawled, or utilize those users and member groups that were modified after the last crawl.

Crawl URL history

A structure that stores a list of URLs and their properties, such as when a URL was last crawled.